#foswiki 2017-05-25,Thu

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

WhoWhatWhen
gac410rramirezm (sorry for delay, I was out to dinner), About spaces in name in left bar. Hover over the name, you should see the un-spaced version of your WikiName in the link. The left bar uses the %SPACEOUT{}% macro to space out the WikiName.
You need to log in as the super user, The left bar should show "Admin User" and not "R Ramirez M".
To log in as admin user, See Main.AdminUser. There is a link there to elevate your login to AdminUser.
It says "internal admin login ( use the password set in configure)"
If that password does not work or is not set, you can set it from the shell. RUN THIS COMMAND AS YOUR WEB SERVER USER. (eg www-data, or apache, depending on the OS)
sudo -u www-data tools/configure -save -set {Password} = 'newadminpassword'
[00:03]
daemonha you can cll configure directly for various stuff, neat [00:07]
gac410If you were to run that command as root, you could possibly knock down your web server by changing ownership of the log files.
daemon. Yes, that was a new feature in Foswiki 2.x Fully scriptable configure. Anything you run from the web bin/configure can also be run from the shell using tools/configure including wizards, set commands, etc.
see Foswiki:System/InstallationGuide#Configuring_Foswiki_manually_40without_using_the_61configure_61_page_41
[00:08]
FoswikiBothttps://foswiki.org/System/InstallationGuide#Configuring_Foswiki_manually_40without_using_the_61configure_61_page_41 [ InstallationGuide ] [00:10]
GithubBot[distro] vrurg pushed 1 new commit to Item13897: https://git.io/vHOuf
distro/Item13897 d85280c Vadim Belman: Item13897: Don't generate extra stack trace on fata exceptions
[00:11]
***GithubBot has left
FoswikiOnSlack has quit IRC (Write error: Broken pipe)
[00:11]
FoswikiBothttps://foswiki.org/Tasks/Item13897 [ Item13897: Implement ImproveOOModel proposal. ] [00:11]
.... (idle for 19mn)
GithubBot[distro] gac410 pushed 2 new commits to Release02x01: https://git.io/vHOz2
distro/Release02x01 6e0a9f4 George Clark: Item13883: Update release notes.
distro/Release02x01 496c0a8 George Clark: Item000: Build 2.1.4-RC3
[00:30]
***GithubBot has left [00:30]
FoswikiBothttps://foswiki.org/Tasks/Item13883 [ Item13883: Documentation changes for master and 2.1 ]
https://foswiki.org/Tasks/Item000 [ Item000 ]
[00:30]
QBFreakack, FoswikiBot is confused
ack! I am confused!
please disregard all ramblings...
[00:33]
FoswikiOnSlack1<rramirezm> Ok if I elevate to admin user there is no problem
<rramirezm> But shouldn't my user RRamirezM have admin privilegies if I'm in the AdminGroup?
[00:45]
gac410Yes. If you visit AdminGroup is it now listed there? Toward the bottom under the heading Members? [00:46]
FoswikiOnSlack1<rramirezm> yes [00:47]
gac410hm so if you log out from AdminUser, and log in as RRamirezM, don't you have admin privileges? [00:47]
daemon<rramirezm> But my leftbar indicates a bit different my name, it says I'm R Ramirez M, with the spaces
is that just showing his 'real name' instead of username
or is there perhaps some user corruption?
[00:48]
gac410That's just a display. The Left bar has the macro %SPACEOUT{%WIKIUSER%}% which breaks on lower-upper boundaries It's just the display [00:49]
daemonah no my name has spaces on the left ba
r
[00:49]
gac410it's just trying to be friendly ;) [00:49]
daemoncould it be that he is using fcgid like me and it has a cache of the old permissions? [00:50]
gac410We don't cache permissions. We *could* cache the rendered display of a page based on your permissions.
If the page cache is enabled (which is NOT the default)
[00:51]
daemonalso could be a mis behaving httpd or client though, cached something it should not have
if he was using a reverse proxy that would not be that difficult
[00:52]
gac410Lets not overcomplicate it quite yet ;) [00:53]
daemon:) [00:53]
gac410foswiki.org is now running Release 2.1.4-RC3 Hopefully this is the winner. No more bug reports please ;) [00:57]
daemonhold on I got 5 or 6 in my notepad
j/k ;D
[00:57]
GithubBot[distro] gac410 tagged FoswikiRelease02x01x04_RC3 at 3560ef1: https://git.io/vHO2M [00:59]
***GithubBot has left [00:59]
GithubBot[distro] gac410 deleted FoswikiRelease02x01x04-RC3 at 9dd3242: https://git.io/vHO2N [01:00]
***GithubBot has left [01:00]
GithubBot[distro] vrurg pushed 11 new commits to Item14237: https://git.io/vHOao
distro/Item14237 7d6d754 Vadim Belman: Item14237: Merge commit '28294f2aef8171f625a535ffd874906da4b0ad82' into Item14237...
distro/Item14237 3874993 Vadim Belman: Item14237: Avoid extra stack trace on exceptions
distro/Item14237 87c0d26 Vadim Belman: Item14237: Cache internal consistency
[01:11]
***GithubBot has left [01:11]
FoswikiBothttps://foswiki.org/Tasks/Item14237 [ Item14237: Implement Development.OOConfigSpecsFormat proposal ] [01:11]
gac410https://foswiki.org/Download/FoswikiRelease02x01x04-RC3 Get it while it's hot! I built upgrade packages this time. [01:11]
vrurggac410: thumbs up! [01:13]
gac410Lets hope we can rename this to 2.1.4 and announce it in a few days. [01:14]
vrurgI though to focus on docs finally but ended up implementing expandables... Now don't even remember what it was needed for! ;)
That's probably subconsciousness is playing game of diverting me from what it doesn't like... ;)
[01:17]
gac410;) Not many devs like to document. [01:18]
vrurgI'm rather ok with it – when it comes to documenting methods in the code. I love the idea of embedded TML (this is why I eventually rewrote INCLUDE's doc handler).
But writing generalized docs is simply beyond my language skills.
[01:21]
daemonI always just document as I write, keep a spare terminal up echo "Some documentation" >> Documentation
tap things in every few hours
no problem!
[01:28]
gac410With the foswiki perl modules it's pretty easy, you can embed TML between perl doc markers =begin TML and =cut [01:29]
vrurgdaemon: Works for a steady dev process. Not when it is possible that the very next day the whole module could be thrashed and redesigned from scratch becose of some unforseen issues... [01:29]
daemonvrurg, actually what I got this wiki for is the first time I have ever tried writing the documentation BEFORE any code
seems to be working pretty well
kinda misusing foswiki a bit but ~ meh
[01:29]
gac410The Foswiki:System.PerlDoc then lets you see the docs that are embedded, nicely formatted. And for admins, it also counts & showd TODO and SMELL [01:30]
FoswikiBothttps://foswiki.org/System.PerlDoc [ PerlDoc ] [01:30]
vrurgBut that's ok, I can document afterwards, when the idea is finally stabilized and implemented. Worse is to describe general concepts in a separate topic.
daemon: This is what foswiki.org has the proposals for.
[01:30]
daemonnah my misuse is the writing style; I am kinda writing in a meta-blog fasion
rather than a 'documentation' style
[01:31]
vrurgBut one could always overlook something, so the eventual implementation would differ from what was planned.
Ok, it looks like my brain is opposing the idea of documenting again. Sure thing, any kind of discussion is always more fun for it! :D
[01:32]
daemon:)
I have 3 monitors on my system, left is IRC/comms middle is work right is webbrowser/netflix/media
it takes me a long time to document stuff too!
[01:33]
vrurgI'm using a single ultra wide one. Less distractstions, more space for Komodo. [01:36]
gac410gac410 sits on my sofa with a laptop :P [01:37]
daemonI quite like having the 'click' for 3 full screen applications
:)
[01:37]
GithubBot[distro] vrurg pushed 2 new commits to Item14237: https://git.io/vHOwX
distro/Item14237 0d2d325 Vadim Belman: Item14237: Some more text.
distro/Item14237 61bf816 Vadim Belman: Item14237: Fixed handling of package with {} syntax
[01:42]
***GithubBot has left [01:42]
FoswikiBothttps://foswiki.org/Tasks/Item14237 [ Item14237: Implement Development.OOConfigSpecsFormat proposal ] [01:42]
vrurgvrurg just cannot completely concentrate on a sofa. Or would rather fall asleep within minutes... [01:43]
daemonthats the one
vrurg, the reassuring ability to not be able to put your feat up at your desk so the inability to get 'to comfy' :)
[01:46]
vrurgdaemon: sorry, that sentense is definitely beyond my English. [01:49]
daemonvrurg, its good you cannot get comfortable enough at your desk top fall asleep :)
s/top/to/
[01:49]
vrurganyway, gac410 – do you know why an anchor #AnchorName in an embedded TML becomes translated into <spand id="AnchorName"></span>? [01:50]
gac410I am very poor with "why" questions. ;) [01:50]
vrurgdaemon: I wouldn't be so sure if I'd be you. ;)
gac410: But you never used anchors there, right?
[01:51]
gac410It might be ... html5 cannot use <a for anchors. [01:51]
daemonit can
ohhh I see
http://geekswithblogs.net/ihaynes/archive/2013/07/12/named-anchors-in-html5.aspx
in html5 your id's are your anchors
[01:52]
vrurg<a class="foswikiCurrentTopicLink" href="#AttrData"><code>data</code></a> – acts as a full-fledged link and opens Foswiki.pm doc (I'm in a PerlDoc generated page) [01:53]
gac410According to w3schools.com "In HTML 4.01, the <a> tag could be either a hyperlink or an anchor. In HTML5, the <a> tag is always a hyperlink, but if it has no href attribute, it is only a placeholder for a hyperlink." [01:54]
vrurgOk, then does Firefox do the right thing by not scrolling down to the <span id="AttrData"> but opening a new page? [01:56]
gac410hm no it should scroll down to the anchor if you include the fragment on the url.
If you find anchors opening new pages, that's a common symptom of misconfiguration of short URLs. And the web server is redirecting bin/view/Web/Page#fragment to /Web/Page#fragment
i see that often with misconfigued foswiki installs. Anchors relaading the page, after 302. bingo - didn't set the {ScriptUrlPaths}{view} = '';
[01:56]
vrurghttps://pastebin.com/b0nV08ZD [02:00]
gac410those look quite normal.
the id= on the h3 is the auto-generated TOC id,
[02:02]
daemontack pastebin.com, there is so many nice alternatives http://paste.ee https://ghostbin.com https://www.pastiebin.com https://gist.github.com [02:03]
FoswikiBot[ Ghostbin ] [ Pastiebin.com index ] [ Create a new Gist · GitHub ] [02:03]
daemonjust saying :) [02:03]
vrurgh3 is there accidentally. [02:04]
gac410Foswiki:System.PerlDoc?module=Foswiki::Func the index seems to reposition just fine without reloading the page. [02:04]
FoswikiBothttps://foswiki.org/System.PerlDoc?module=Foswiki::Func [ PerlDoc ] [02:04]
vrurgThe index is using this: <a href="?module=Foswiki::Config#A_61ObjectMethod_61_61_61get_40_41_61_61"> [02:05]
FoswikiBothttps://trunk.foswiki.org/System/PerlDoc?module=Foswiki::Config [02:05]
vrurgThe difference is in missing "?module=" when [[#Anchor]] is used. Perhaps URLPARAMS is required but it overcomplicates such a simple approach!
Yet I always thought that with <a href="#Anchor"> a browser must not reload the page but simply scroll it to the desired position.
[02:06]
gac410I thought too so. [02:08]
vrurgThe problem seems to be in presence of url params. Firefox ignores them and simly forms full URL for href="#Anchor" without them. Then it finds out that it's different from current page URL – and reopens.
I'll leave it as is for now. Time to rest and have some beer. cu!
[02:16]
gac410cu [02:16]
vrurg. ... You've found a bug. TOC is smart enough to include ?urlparam=foo#fragment [[#fragment]] does not. [[ ]] needs to render anchors differently I think. [02:26]
daemonseems to be the season :) [02:29]
gac410I'm not going to try to tackle this for 2.1.4 [02:29]
daemon2.1.4 already shipped I thought
ah rc3
[02:31]
gac410I like to at least let it soak on f.o for a few days before publishing the final release. [02:32]
daemongotcha
hmm I will have to update mine I am on RC1
will wait for the full release though
[02:32]
gac410The original task on TOC anchors is Item5987 Dates to TWiki [02:33]
FoswikiBothttps://foswiki.org/Tasks/Item5987 [ Item5987: relative TOC anchors get prepended with parameters which may trigger a page reload ] [02:33]
gac410I generated "update" packages for RC3 [02:33]
daemonah
so you think I should hop to RC3 then grab -RELEASE when it comes out so the jump is not as large
[02:34]
gac410Up to you if you want to give it a try. *hopefully* there will be no changes, so I rerun build.pl to change the release / version strings and re-release.
for upgrading foswiki.org, I don't use the update package. I use https://github.com/foswiki/distro/blob/master/core/tools/foswiki-upgrade-check
But we have modified files that the update package would overlay.
[02:36]
daemonbrb -- as a laugh I had a dark idea yesterday of starting my own fork for 4.x and trying to remove CGI ;) [02:40]
gac410sudo -u www-data ./foswiki-upgrade-check -y -b bkup -f /var/www/foswiki.org/ Foswiki-2.1.4-RC2/ Foswiki-2.1.4-RC3/
though the "bkup" directory needs to be owned by www-data
anyway [[?%QUERYSTRING%#fragment]] might work. *but* it could be dangerous to copy the query string into a url. so needs some consideration.
[02:40]
................ (idle for 1h19mn)
vrurg: Opened task Item14407 to address the reseting anchor issue. [04:02]
FoswikiBothttps://foswiki.org/Tasks/Item14407 [ Item14407: Page relative Anchor links don't pick up query params, resulting in param reset and page reload. ] [04:02]
gac410with that .. g'night [04:02]
***gac410 has left
ChanServ sets mode: +o gac410
gac410 changes topic to: Download: **NEW RC: https://foswiki.org/Download/FoswikiRelease02x01x04-RC3 ** Logs: http://irclogs.foswiki.org/bin/irclogger_log/foswiki - Slack: https://foswiki-slackin.herokuapp.com/ - Bugs: https://foswiki.org/Tasks - Next Release meeting Monday 29 May 2017, 1300Z
[04:02]
....................................................................................... (idle for 7h13mn)
ChanServ sets mode: +o Lynnwood [11:16]
.................. (idle for 1h27mn)
ChanServ sets mode: +o gac410 [12:43]
.............................. (idle for 2h28mn)
FoswikiOnSlack1<rramirezm> @rramirezm Hi sorry, felt asleep yesterday, and just as you say, I don't have admin privileges even when i'm in the group AdminGroup [15:11]
gac410What Mapper are you using? The default is $Foswiki::cfg{UserMappingManager} = 'Foswiki::Users::TopicUserMapping'; [15:13]
FoswikiBothttps://trunk.foswiki.org/System/PerlDoc?module=Foswiki::Users::TopicUserMapping [15:13]
FoswikiOnSlack1<rramirezm> let me check
<rramirezm> I have that one
<rramirezm> TopicUserMapping
[15:14]
gac410What is $Foswiki::cfg{UsersWebName} set to? Should be "Main"
If you changed it, then the AdminGroup topic that's used is in whatever web is configured for UsersWebName
[15:16]
...................... (idle for 1h45mn)
GithubBot[distro] gac410 pushed 2 new commits to Item14343: https://git.io/vH3hb
distro/Item14343 1be0dae George Clark: Item14343: Another GroupViewTemplate include needs adjusting.
distro/Item14343 c035a5f George Clark: Item14343: Add a warning if in a non-active Main web.
[17:02]
***GithubBot has left [17:02]
FoswikiBothttps://foswiki.org/Tasks/Item14343 [ Item14343: Minor topic rearranging to further simplify upgrades. ] [17:02]
................... (idle for 1h32mn)
FoswikiOnSlack1<rramirezm> Back, It's value is Main
<rramirezm> its*
[18:34]
........... (idle for 52mn)
gac410rramirezm ... you've completely exhausted any ideas that I had. I have no idea why AdminGroup is not giving you admin rights. This is used very widely and I've never seen any issues in this area. [19:27]
.... (idle for 17mn)
FoswikiOnSlack1<rramirezm> any kind of logs I can send you? [19:44]
gac410Is this a new install or an old migrated site from Foswiki 1.x or TWiki? [19:44]
FoswikiOnSlack1<rramirezm> new install
<rramirezm> but i do have some problems
<rramirezm> i need to stop start
<rramirezm> i get errors
<rramirezm> do again stop start the service
<rramirezm> and now it works
<rramirezm> maybe i'll install fresh again
[19:45]
gac410Apache? Nginx?
What is your web server? Apache? Nginx? Lighttpd?
And OS - Linux? any particular flavor?
[19:45]
FoswikiOnSlack1<rramirezm> Nginx
<rramirezm> Ubuntu 16.04
[19:49]
gac410And you installed Foswiki 2.1.3 ?
There is an updated sample nginx configuration at Foswiki:System/FastCGIEngineContrib, and an updated init script and defaults file at https://github.com/foswiki/distro/tree/master/FastCGIEngineContrib/tools
[19:50]
FoswikiBothttps://foswiki.org/System/FastCGIEngineContrib, [19:52]
FoswikiOnSlack1<rramirezm> that's the one i used [19:53]
gac410And you are getting an error from Foswiki and not a nginx denied message?
I've got a VM with nginx on it. I'll set this all up again using the examples I just pointed to and see if I can see anything wrong. I don't use nginx much, and the devel who does most with it is not around.
[19:54]
FoswikiOnSlack1<rramirezm> Should I send you my nginx conference
<rramirezm> configuration*
[20:02]
gac410For now let me just use the defaults we ship and see how it goes. I didn't have a 16.04 vm available but I have a 16.10, but that should be close enough. Just installed nginx-full [20:03]
FoswikiOnSlack1<rramirezm> ok
<rramirezm> the error I get is that perl gets stuck as listening to :9000
[20:04]
gac410okay. So when you stop foswiki, it fails to actually stop? [20:06]
FoswikiOnSlack1<rramirezm> no
<rramirezm> the journalctl says successfully stopped
[20:06]
gac410does a ps -aux | grep foswiki show it? [20:07]
FoswikiOnSlack1<rramirezm> but if I throw a netstat -ntl
<rramirezm> the port :9000 says perl is ussing it
<rramirezm> the error in the journalctl is
<rramirezm> bind/listen :Address already in use
<rramirezm> foswiki.service: Control process exited , code=exited status=1
<rramirezm> sudo netstat -nltp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1862/perl
<rramirezm> Then i can either kill that process or just run again
<rramirezm> Sudo service foswiki stop Sudo service foswiki start
<rramirezm> and It'll work
[20:07]
gac410strange. Let me see what happens here [20:12]
FoswikiOnSlack1<rramirezm> ok [20:13]
gac410did you install the foswiki.service file, or did you use the traditional foswiki init script. Either should work [20:16]
FoswikiOnSlack1<rramirezm> let me check
<rramirezm> the one that goes into /etc/default
<rramirezm> is the service?
[20:17]
gac410There are two files. etc/default/foswiki and etc/init.d/foswiki The latter is the traditional init script
There is also a systemd/foswiki.service that can be used, but IMO the init script is simpler.
[20:18]
FoswikiOnSlack1<rramirezm> i used the one that goes in etc/default/foswiki [20:25]
gac410rramirezm that is just the defaults. It's not an initt script. Do you also have a file /etc/init.d/foswiki ? [20:26]
FoswikiOnSlack1<rramirezm> yes i have that one too [20:28]
gac410okay. I've recreated the stuck process. No idea why that's happeing, but indeed it does not stop with a service foswiki stop. [20:29]
FoswikiOnSlack1<rramirezm> I don't that that's related to my Admin rights process
<rramirezm> also i meddled a bit with the wiki name logging name
[20:30]
gac410Okay. I know what's going on wit the stuck task. There is an optional perl module required apt-get install libfcgi-procmanager-perl [20:31]
FoswikiOnSlack1<rramirezm> let me install it
<rramirezm> and see
[20:32]
gac410Thats the process manager required to stop/start the fcgi backends There are two modules required for foswiki using fcgi:
FCGI libfcgi-perl Optional, needed for fastcgi / fcgi apache modules
FCGI::ProcManager libfcgi-procmanager-perl Optional, needed for fastcgi / fcgi process management
[20:33]
FoswikiOnSlack1<rramirezm> looks like it was generated again
<rramirezm> but i didn't restart the nginx service
<rramirezm> nor the php-service
[20:35]
gac410foswiki does not use php. regarding fcgi, When I installed the libfcgi-procmanager-perl, stopped and killed foswiki, and then started it again, it now stars 3 backend processes and then end correctly when stopping the service.
So without procmanager, I recreated your stuck task. after cleaning it up, and installing procmanager, its working fine.
sorry ... i have to step away ... suppertime here.
[20:37]
Okay... I just tried the AdminGroup thing I registered 2 users JoeUser and FredFlint FredFlint is in the AdminGroup. JoeUser is not.
FredFlint is able to view System.RemoveUsers and is able to access configure.
[20:47]
FoswikiOnSlack1<rramirezm> mmm [20:51]
gac410I then updated Configure - Security and Authentication -> Access Control key {FeatureAccess}{Configure} and set it to JoeUser. [20:51]
FoswikiOnSlack1<rramirezm> Maybe I'll do a fresh install [20:51]
gac410Now JoeUser has access to Configure. And FredFlint, while he is in the AdminGroup does NOT.
Because {FeatureAccess}{Configure} overrides any consideratoin of the AdminGroup for configure access.
[20:52]
FoswikiOnSlack1<rramirezm> OK
<rramirezm> ok
[20:54]
gac410I really have no idea why your AdminGroup topic is not being considered. Could you paste the data/Main/AdminGroup.txt file to http://pastebin.com ... set it or a short expiration [20:54]
FoswikiOnSlack1<rramirezm> ok [21:00]
gac410and send me the link ;) [21:00]
..... (idle for 21mn)
FoswikiOnSlack1<rramirezm> @gac410 https://pastebin.com/Ww3PCnAe [21:21]
gac410That looks perfectly normal. The "operative line" is
%META:PREFERENCE{name="GROUP" title="GROUP" type="Set" value="RRamirezM, PedroCarriles"}%
And on my test wiki its:
%META:PREFERENCE{name="GROUP" title="GROUP" type="Set" value="FredFlint, JoeUser"}%
nothing wrong there. Have you tried both IDs RRamirezM and PedroCarriles Neither of them can access System.RemoveUser ?
Ah... .one more config setting to check in lib/LocalSite.cfg
What is the AdminGroup set to:
$Foswiki::cfg{SuperAdminGroup} = 'AdminGroup';
Is what it should be.
That has to be set to the name of the Main topic that is the Admin group.
[21:23]
.... (idle for 15mn)
FoswikiOnSlack1<rramirezm> let me check
<rramirezm> It's set to AdminGroup
<rramirezm> checking the LocalSite
[21:42]
gac410Do you have LoginNames enabled?
$Foswiki::cfg{Register}{AllowLoginName} = 0;
I don't believe it would make a differece, but in a default TopicUserMapping setup, loginnames are usually not used.
With AllowLoginName disabled, which is the default, your WikiUsers topic should have a line for each user, like:
  * RRamirezM - RRamirezM - 25 May 2017
there is a way to monitor ACL processing. It's ugly internals, but maybe it might give a hint.
in lib/Foswiki/Access/TopicACLAccess.pm there is a line at the top: use constant MONITOR => 0; Change the 0 to a 1 to enable ACL tracing.
Then it will dump all sorts of information to the fcgi error log.
You have to restart the foswiki fcgi backend if you change that code setting.
[21:48]
FoswikiOnSlack1<rramirezm> It is activated [22:02]
gac410I'm not sure even what to look for. Maybe you'll see something that gives you a hint. I've almost never had to enable this. [22:03]
FoswikiOnSlack1<rramirezm> i'll disable that [22:03]
gac410This just doesn't make sense. this is an area that should "just work" [22:04]
FoswikiOnSlack1<rramirezm> If it's to late for you
<rramirezm> we can see it tomorrow
[22:04]
gac410dinner cooking. I'll probably break away to eat soon. [22:04]
FoswikiOnSlack1<rramirezm> ok ok [22:04]
gac410About all I've got left is to suggest a clean reinstall. Nothing I can think of would cause this other than the various settings I mentioned. And none of them are something you would normally change. [22:05]
***ChanServ sets mode: +o TravisBarker [22:14]
TravisBarkermoin [22:14]
FoswikiOnSlack1<rramirezm> https://pastebin.com/tUdGgu8E
<rramirezm> heres is the contents of my localsite.cfg
[22:28]
gac410Okay. You do have AllowLoginName enabled. When you log in, do you use rramirezm or RRamirezM
Looking at WikiUsers, you have 3 id's who do not seem to be using loginname and two that are.
loginname is usually only used when there is a backend like LDAP or some other external authenticator. For a normal TopicUserMappping with template login, its best to disable AllowLoginName
[22:37]
FoswikiOnSlack1<rramirezm> RRamirezM
<rramirezm> Ok i'll disable it
[22:43]
gac410I'm trying to recreate your config now
Just about to register
nope... still working. I typoed your name. but Wikiusers has RRamirezR - rramirezr - 25 May 2017 I logged in with the lowercase rramirezr and AdminGroup is working fine.
YIKES ... you pasted the file and it contained some passwords. you need to change your email password ASAP
well it had a 5-minute expires, and it's gone, but still probably would be best to reset your passwords.
[22:43]
.... (idle for 17mn)
Is there any chance your browser is caching the denied page. Try a shift-reload or use another client. Maybe you should pastebin your nginx config. [23:12]
.... (idle for 15mn)
FoswikiOnSlack1<rramirezm> actually it happens in two different computers
<rramirezm> And we did meddle with the users
<rramirezm> I changed manually my loggin name
<rramirezm> by editing the topic
<rramirezm> WikiUsers
<rramirezm> I'll erase those names
<rramirezm> and add them again
[23:27]
gac410hm that topic can be very dangerous to edit. It can be done, but minor changes in layout can break the mapper [23:29]
FoswikiOnSlack1<rramirezm> what should be the bestr
<rramirezm> fresh install
<rramirezm> or just erase the names
<rramirezm> users*
[23:30]
gac410You could just copy the Main/WikiUsers.txt from the distribution
There do seem to be some formatting issues at the bottom with the way the foswikiHelp <div> is laid out. But that part past the footer should not impact things.
Or try restoring Revision 2 of that topic. More topic actions has a menu to restore an old rev.
See https://wiki.hatandslash.com/System/FAQRebuildingWikiUsersTopic An admin can use that to rebuild the WikiUsers topic.
It searches the mapping manager to find the IDs from the htpasswd file and will figure things out hopefully.
[23:32]
.... (idle for 16mn)
***ChanServ sets mode: +o Lynnwood__ [23:52]

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