|↑back Search ←Prev date Next date→ Show only urls||(Click on time to select a line by its url)|
|FoswikiOnSlack1||<rramirezm> It's jus clicking in UpdateWikiUsers am I right?||[00:08]|
|gac410||when you view that topic as admin, it will show you in the text box what it thinks a correct WikiUsers topic should look like.
And if you think it seems okay, then click the UpdateWikiUsers to save over the topic.
|FoswikiOnSlack1||<rramirezm> some of my users losse their loggin name
<rramirezm> * PedroCarriles - - 24 May 2017 - 02:40
|gac410||You disabled AllowLoginName? so that's right. If you want to use Login Names then re-enable that setting.
You cannot mix things though. Either all users use a loginname or all users use their WikiName to log in.
It's a site-wide configuration.
<rramirezm> but other users do have them
|gac410||well set AllowLoginName back on, and see what the Rebuilding topic proposes then.||[00:17]|
<rramirezm> everybody gets their logging name
<rramirezm> if i deactivate it
<rramirezm> should erase them
|gac410||The format of the file is either WikiName - WikiName or WikiName - loginname||[00:22]|
|FoswikiOnSlack1||<rramirezm> and that didn't happen
<rramirezm> again 2 users still have their loggin names
|gac410||I don't really know. I almost never have used loginname||[00:23]|
|FoswikiOnSlack1||<rramirezm> i'll deactivate it||[00:23]|
|<rramirezm> hmm it no longer is erasing the loghing names
|.... (idle for 17mn)|
|<rramirezm> IT WORKED
<rramirezm> the user finally has admin rights
|FoswikiOnSlack1||<rramirezm> Thank you so much||[00:50]|
|gac410||you're welcome. Sorry it was such a chore.||[00:52]|
|FoswikiOnSlack1||<rramirezm> nah it's alwasys like thtat||[00:53]|
|<rramirezm> If someone wanted to change its name
<rramirezm> acording to the documentation
<rramirezm> i have to update the topic name am i right?
|gac410||Actually changing wikinames is not really supported.
Their name is embedded into the topic history of any topics they edit. So the name would live on in history
Best is to just register the new name, and remove the old user, *but* leave the user's topic in the Main web so that history will link to the old user, maybe with a comment that the user has a new name
fixing history is very difficult.
|FoswikiOnSlack1||<rramirezm> oh ok
<rramirezm> And should be added in the user's old name topic
<rramirezm> Named before as "JhonDoe"
<rramirezm> Could you explain the SafePath
<rramirezm> I haven't configured that variable, because i'm unable to understand it
|gac410||okay. That's just the system directories where you want foswiki to look for executables. Under Apache it's set automatically from the PATH but not under nginx
So typically /usr/bin:/bin
Some systems might also want /bin:/usr/bin:/usr/local/bin whatever search order works for your particular installation
colon (:) is the separator between directories.
|FoswikiOnSlack1||<rramirezm> should i set it up under /user/bin?
<rramirezm> or just /bin
|.... (idle for 18mn)|
|gac410||On linux it's usually /bin:/usr/bin (usr not user!)
"fgrep" is in /bin grep is in /usr/bin etc. Those directories are save in that users cannot change them.
er ... "safe" not save/
|FoswikiOnSlack1||<rramirezm> ok ok
<rramirezm> i''ll check it
|............. (idle for 1h4mn)|
|GithubBot||[distro] vrurg pushed 3 new commits to Item14237: https://git.io/vHGne
distro/Item14237 e9c905e Vadim Belman: Item14237: Added support for pluggable methods....
distro/Item14237 1d26d3c Vadim Belman: Item14237: Stability improvements.
distro/Item14237 a78679a Vadim Belman: Item14237: Documenting Foswiki::Config
|***||GithubBot has left||[02:53]|
|FoswikiBot||https://foswiki.org/Tasks/Item14237 [ Item14237: Implement Development.OOConfigSpecsFormat proposal ]
|.............. (idle for 1h9mn)|
|***||gac410 has left||[04:02]|
|......................... (idle for 2h1mn)|
|ChanServ sets mode: +o MichaelDaum||[06:03]|
|.................................................................... (idle for 5h38mn)|
|ChanServ sets mode: +o MichaelDaum_||[11:41]|
|.................. (idle for 1h26mn)|
|ChanServ sets mode: +o gac410||[13:07]|
|..... (idle for 23mn)|
|gac410||hi MichaelDaum_ If you're around, I have a question on weasyprint||[13:30]|
Works great on 2.1.4 ... but I tried it on a 1.1.9 system and it generates truncated PDFs. 1st page blank, 2nd page looks good, and 3rd page is just the web pages footer.
And that's it. I've just been testing with some of the System web topics - InstallationGuide, etc.
Also did you ever do any work with CharsetConverter and VirtualHostingContrib web sites? IIRC it won't work with them.
having looked now at virtual hosting on nginx, I can understand why you like VHC. Unlike apache, you have to build custom init scripts for each virtual host :P It's much easier in apache.
Anyway, that's my stashed questions for the day ;)
|MichaelDaum||the most important reason for VHS is sharing a single foswiki.fcg among all vhosts.
this scales a lot better than having one per vhost
as well as one single code base for all
nginx configs are generated automatically based on VHC's configuration
everytime I do a "service nginx reload/restart"
|gac410||yup. that became obvious once I started trying to build the custom init scripts for testing. lots to get right. Single code base I'm not so enamored of... I prefer to update only one system at a time. Expecially this time with complexity of charset converter and many extensions to test.||[13:37]|
|MichaelDaum||next big advantage of nginx over apache: separation of http and foswiki; much better control over lifecycles of foswiki backends; when foswiki crashes the rest of the http services are still alife, and vice versa.
charset conversion: you do it once and forget about it from there one
|gac410||WHAT!!! Foswiki? Crash??? never :D||[13:38]|
|gac410||Right. but conversion is a daunting task with a dozen vhosts on a single 1.1.9 instance. with VHC I somewhat have to do the whole darn thing at once.||[13:40]|
|MichaelDaum||did you use the tools/virtualhosts-convert-charset script?
part of VHC
|gac410||Oh.... didn't know about that.||[13:41]|
|MichaelDaum||vhost frontend to charset converter
a single script to run on all vhosts in one go
|gac410||Gah... With unknown data on an unfamiliar website, I had planned to do one web at a time on one vhost at a time. carefully inspecte each web when converted, run the ACL converter, test, and move on to the next web.||[13:43]|
|MichaelDaum||... as long as you get paid for the time spent||[13:43]|
|MichaelDaum||then don't tell anybody there was an easier way||[13:43]|
|gac410||easier?? When I did Foswiki.org, it took hours to find and fix the crashing webs due to bogus data.||[13:44]|
|MichaelDaum||yea: those ms word copy die hards create all sorts of problems in that vein||[13:45]|
|gac410||I'd much rather be methodical and get it done right the first time. I can't imagine blindly converting the entire world in one pass is easier/faster unless the data is clean.
And with my experiences the data is seldom clean. :(
|MichaelDaum||of course this is totally up to you
MichaelDaum things of all those <font> tags and <span style="yadda"> created by wysismock
|gac410||Running charset converter with the charset set to cp-1252 gets it to work pretty well||[13:47]|
|***||ChanServ sets mode: +o Lynnwood||[13:48]|
|gac410||So the ACL converter. I don't think that will work with the VHC ... do you just enable the deprecated empty deny rules and ignore the rest?||[13:48]|
|MichaelDaum||most sites I've set up to use 1.1.9 those days had already their site charset on utf-8 ... so migrating them to foswiki-2 did not require any charset conversion ...||[13:48]|
|gac410||Ah... that simplifies things greatly.
Oh... back to my WeasyPrint question. Any known issues on 1.1.9? Is it me ... generating truncated 3-page PDFs
flawless on 2.1.4
|***||ChanServ sets mode: +o Lynnwood__||[13:50]|
|gac410||So I know it's not my weasyprint installation||[13:50]|
|MichaelDaum||can't say. could be a css issue in PatternSkin
I vaguely remember there was somebody reporting the same, years ago...
|gac410||okay. It's not worth trying to fix. Just curious. I'll just hold off on the pdf generation update until after the 2.1.4 conversion.||[13:52]|
|MichaelDaum||maybe it helps installing a newer PatternSkin...||[13:52]|
|gac410||hm the 2.x pattern skin iirc has some significant compatibilitiy issues on 1.1.9||[13:53]|
|MichaelDaum||ah ok. then better hold off.||[13:53]|
|daemon||for the lols :) https://www.sudosatirical.com/articles/systemd-set-to-declare-independance/||[13:54]|
|gac410||At one point I generated a bunch of pattern01x01 templates to keep it compatible. But I've not kept up testing.||[13:55]|
|daemon||gac410, an exciting step in my insanity project; https://paste.ee/p/LkgH4 I have my natural PK's :) now I am just trying to harass every DBA I know to try figure out a way to store all this crap sanely -_-||[13:55]|
|gac410||:) Better you than me
Anyway MichaelDaum ... thanks for lending an ear and your advice.
|daemon||I managed to get 3 competing ideas on howto do it||[13:59]|
|gac410||MichaelDaum: When did you last use the vhc charset converter? I was just looking at the code It calls Foswiki::Contrib::CharsetConverterContrib::convertCollection
But if I grep for convertCollection in CharsetConverterContrib. it isn't there.
|gac410||either that or I'm losing my mind. Well it is there, but in a unit test, not in the main module.||[14:13]|
|MichaelDaum||seems as if this got renamed to convert_database :(--||[14:14]|
|gac410||y. Done by cdot back in june 6b98521f7ef43f766ca7115b6bf6d6a1ee2d3e62
|***||ChanServ sets mode: +o Lynnwood||[14:25]|
|..... (idle for 21mn)|
|ChanServ sets mode: +o Lynnwood__||[14:46]|
|ChanServ sets mode: +o Lynnwood||[14:58]|
|ChanServ sets mode: +o Lynnwood__||[15:11]|
|ChanServ sets mode: +o Lynnwood||[15:19]|
|............ (idle for 57mn)|
|daemon||gac410, windows at its finest, https://itsosticky.com/8obptg
~I really should just use freebsd as a desktop -_-
|***||ChanServ sets mode: +o Lynnwood__||[16:28]|
|ChanServ sets mode: +o gac410||[16:38]|
|...................... (idle for 1h46mn)|
|ChanServ sets mode: +o Lynnwood||[18:24]|
|↑back Search ←Prev date Next date→ Show only urls||(Click on time to select a line by its url)|