#foswiki 2017-03-27,Mon

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***ChanServ sets mode: +o Lynnwood__ [00:29]
............................................................ (idle for 4h56mn)
ChanServ sets mode: +o cdot [05:25]
........ (idle for 38mn)
GithubBot[distro] MichaelDaum pushed 1 new commit to Item14288: https://git.io/vSL2m
distro/Item14288 fd9adbe MichaelDaum: Merge branch 'master' into Item14288
[06:03]
***GithubBot has left [06:03]
FoswikiBothttps://foswiki.org/Tasks/Item14288 [ Item14288: rewrite to support pluggable edit engines ] [06:03]
***ChanServ sets mode: +o cdot
ChanServ sets mode: +o MichaelDaum
[06:05]
................ (idle for 1h16mn)
foswiki_irc5Hello! Can you help me? I have a problem with the Foswiki access control. [07:21]
jastmaybe :) what's the problem? [07:22]
foswiki_irc5i wrote the details here: http://stackoverflow.com/questions/43017910/foswiki-user-topic-only-visible-for-1-user-and-admins [07:23]
jastfoswiki_irc5: you should be able to use the same approach as in the original System.NewUserTemplate, only adding a similar line for ALLOWTOPICVIEW [07:35]
..... (idle for 22mn)
foswiki_irc5I chanded it. After registration, my test user's topic has the Set ALLOWTOPICVIEW= Main.MyTestUser line in it. I'm still not able to view or edit it.
You can see the topic source here : http://pastebin.com/nHsyKnsQ
In the documentation near the ALLOWTOPICVIEW keyword, the say: Caution As with the the prior example, this is set in the "Topic Settings" and not inline in the topic text!
I see difference between the topic source and the access settings on the GUI. In source, I successfully set up my test user to view his topic.
On the Settings/AC page: only NewUserTemplate user/group can view the topic, which is clearly not my test user.
[07:57]
.................................................. (idle for 4h6mn)
***ChanServ sets mode: +o gac410 [12:14]
foswiki_irc5I managed to solve the problem. It turned out that the GUI AC settings has priority over the topic source settings. I choosed the default VIEW access, than saved the template. Now it works! Thank you for your instruction jast! [12:23]
***ChanServ sets mode: +o Lynnwood [12:32]
gac410Hi all ... Is there anybody online who uses the HttpsRedirectPlugin ... I've got some enhancements I'm considering, mainly for foswiki.org. [12:39]
............................................. (idle for 3h43mn)
GithubBot[distro] MichaelDaum pushed 1 new commit to Item14288: https://git.io/vSt1f
distro/Item14288 1908535 MichaelDaum: Item14288: added tinymce_native engien...
[16:22]
***GithubBot has left [16:22]
FoswikiBothttps://foswiki.org/Tasks/Item14288 [ Item14288: rewrite to support pluggable edit engines ] [16:22]
....... (idle for 34mn)
***gac410 sets mode: +v FoswikiBot [16:56]
......... (idle for 41mn)
ChanServ sets mode: +o MichaelDaum [17:37]
.... (idle for 15mn)
ChanServ sets mode: +o Lynnwood__ [17:52]
............................ (idle for 2h17mn)
jmk0MichaelDaum: I noticed the GraphvizPlugin lacks classification and a short description on this page: https://foswiki.org/Extensions/AllExtensions
version information as well
[20:09]
..... (idle for 23mn)
gac410jmk0: The version info is missing because the search is trying to get it using a regex. Need to change to a formfield. Classification, I just added. [20:33]
jmk0ok, thanks
I had to dig a bit to find it since it wasn't showing up in the "short list"
[20:39]
gac410Okay. I've fixed the versions as well. Extensions web used to be plain old regex extraction of * Set... bullets. Now the data is in formfields. [20:40]
jmk0thanks :)
it's showing up in the extensions webhome now, too.
just to confirm
[20:41]
gac410good. thanks.
All the pdf extensions were missing classification too,.
[20:42]
jmk0ha, looks like my own DataFlowDiaPlugin is missing classification as well :-./ [20:43]
gac410;) [20:43]
jmk0hum, any suggestions what classification is appropriate for AutoSubPlugin? It replaces text at render time based on macro settings
.. and should I be editing this directly on f.o or should I fix it in github?
[20:46]
gac410Edit the form data on foswiki.org. The upload script downloads it to recover the form, and then restores it before upload.
At least it used to work that way ;)
[20:47]
.......................... (idle for 2h9mn)
vrurgIf I ever be asked what annoys me most about foswiki my answer will be "the error 403, invalid validation code"... :( [22:56]
gac410y. pita at times.
Especially wait too long - it times out, and that long involved comment gets rejected.
[22:56]
vrurgWish I put my hand on it. Do you know the reason why the code gets timed out? And why the valid period is that short? [22:58]
gac410I think the valid period is configurable. ... I don't recall now.
$Foswiki::cfg{Validation}{ValidForTime} = 3600; Default is an hour. Prevents someone from discovering/reusing keys
At least that's the theory
There is also a limit of keys stored per session. (1000). after that keys are forced expired. This is all documented in configure / Foswiki.spec
[22:59]
vrurgIt is only the theory. On my work setup it is often follows the following scenario: open a page, read, comment -> fail. All strictly within 10-15 minutes.
I can't generate 1000 keys in just an hour. :)
[23:02]
gac4102.1.3? Or an older version. There was a bug at one point where the cache was storing the stale keys [23:03]
vrurgOk, forget about it. I was just wining. [23:03]
gac410So if you view a page, then come back tomorrow, view & comment, it would use yesterday's key. [23:04]
vrurgs/wining/whining/ [23:04]
gac410You can certainly turn strikeone off [23:04]
vrurgI thought it was fixed in 2.1.3 already. Ok, got it wrong then. Though this time this same error happend to me on foswiki.org [23:05]
gac410yes. that was fixed in 2.1.3 Item14150 [23:06]
FoswikiBothttps://foswiki.org/Tasks/Item14150 [ Item14150: Reload of a page in the cache fails to recompute strikeone keys. ] [23:06]
gac410Just commenting that could cause the failed strikeone in a short time. [23:06]
vrurgOk, ignore it. Though my first note was because it happend to me on foswiki.org but I don't want to waste time on it. At least now. [23:07]
gac410I'm not sure what could else could cause the issue.
foswiki.org might be caused if you get the strikeone cookie as secure. and then visit with non-https.
I had to delete cookies the other day because strikeone got "stuck"
Oh... but that was on my test server.
[23:07]
vrurgAndI I don't wanna switch the feature off – still better be on the safe side. Better copy the failed comment and reload the page. [23:09]
...... (idle for 27mn)
GithubBot[distro] gac410 pushed 2 new commits to master: https://git.io/vSqFb
distro/master f85590f George Clark: Item14339: Convert WebTopicCreator to canoncial SCRIPTURLPATH
distro/master c8341b8 George Clark: Item13948: Convert to relative links...
[23:36]
***GithubBot has left [23:36]
FoswikiBothttps://foswiki.org/Tasks/Item14339 [ Item14339: Implement ContinueCanonicalSCRIPTURLDev ]
https://foswiki.org/Tasks/Item13948 [ Item13948: Implement UseRelativeLinksByDefault ]
[23:36]
GithubBot[distro] gac410 pushed 1 new commit to Release02x01: https://git.io/vSqFN
distro/Release02x01 19ec615 George Clark: Item13246: Document the header/body/footer contexts.
[23:37]
***GithubBot has left [23:37]
FoswikiBothttps://foswiki.org/Tasks/Item13246 [ Item13246: Context =header_text= needs better documentation ] [23:37]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)