#foswiki 2017-01-24,Tue

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

WhoWhatWhen
gac410Foswiki.org has had it's Cookie Domain changed to a wildcard.
- If login returns you back to the login page, you need to clear your cookies and try again.
- If you are trying to access trunk.foswiki.org, you need to clear your cookies as well.
We need to implement Foswiki:Development/ConfigurableCookieNamesAndPaths at least on trunk, ASAP.
[01:57]
FoswikiBothttps://foswiki.org/Development/ConfigurableCookieNamesAndPaths [ ConfigurableCookieNamesAndPaths ] [01:57]
................ (idle for 1h15mn)
GithubBot[distro] gac410 created Item14301 (+1 new commit): https://git.io/vMFwR
distro/Item14301 7c91e29 George Clark: Item14301: Implement ConfigurableCookieNamesAndPaths...
[03:12]
***GithubBot has left [03:12]
FoswikiBothttps://foswiki.org/Tasks/Item14301 [ Item14301: Implement ConfigurableCookieNamesAndPaths ] [03:12]
...................... (idle for 1h45mn)
GithubBot[distro] gac410 pushed 1 new commit to Release02x01: https://git.io/vMFX0
distro/Release02x01 3ed69a5 George Clark: Item13883: Update Release Notes for new release...
[04:57]
***GithubBot has left [04:57]
FoswikiBothttps://foswiki.org/Tasks/Item13883 [ Item13883: Documentation changes for master and 2.1 ] [04:57]
GithubBot[distro] gac410 pushed 1 new commit to master: https://git.io/vMFXw
distro/master a3adc9f George Clark: Item13883: Merge branch 'Release02x01'
[04:59]
***GithubBot has left [04:59]
GithubBot[distro] gac410 pushed 1 new commit to Release02x01: https://git.io/vMFXF
distro/Release02x01 68dfe2e George Clark: Item13883: Topic name missing from documentation.
[05:07]
***GithubBot has left [05:07]
GithubBot[distro] gac410 pushed 1 new commit to master: https://git.io/vMFXb
distro/master 3a8d538 George Clark: Merge branch 'Release02x01'
[05:07]
***GithubBot has left [05:07]
...... (idle for 27mn)
gac410 has left [05:34]
.............. (idle for 1h9mn)
FoswikiOnSlack<itaki> Hello Foswiki world.
<itaki> Here is my foswiki website, my second love :slightly_smiling_face: :
<itaki> https://istenovaisguvenligi.com/
<itaki> Unfortunately, my website suddenly collapsed yesterday night.
<itaki> As you can see, we can not reach to the site.
<itaki> My hosting is :
<itaki> https://www.tmdhosting.com/
<itaki> I think this failure is related with hosting service.
<itaki> What I did yesterday night is just to try to upgrade 4 different plugins which have more recent releases.
<itaki> I did above mentioned operatin from "configure".
<itaki> When I saved my revisings and when I returned to my website, I couldn't reach it.
<itaki> I will be very glad if you help me for above mentioned issue.
<itaki> TMD Hosting "Genius Support Team" is already working on it.
<itaki> I am afraid some of my data kept in my website will be lost when they try to recover the site from backups.
<itaki> Do you have any suggestion?
[06:43]
uebera||itaki: Looks like a dependency is not met or the like--you need to search your server's logs for the Foswi "serializer not implemented" error message which will be more detailed there.
Which plugins did you upgrade? Have you checked whether they now require additional Perl modules? (configure should have told you so, normally)
[06:56]
**** FYI: If you cannot get logged in on foswiki.org, clear your cookies for foswiki.org and retry. The Foswiki Cookie Domain has been changed. **** [07:04]
GithubBot[distro] MichaelDaum pushed 1 new commit to Item14288: https://git.io/vMFHZ
distro/Item14288 1872092 MichaelDaum: Item14288: Merge branch 'master' into Item14288
[07:07]
***GithubBot has left [07:07]
FoswikiBothttps://foswiki.org/Tasks/Item14288 [ Item14288: rewrite to support pluggable edit engines ] [07:07]
.... (idle for 19mn)
***ChanServ sets mode: +o cdot [07:26]
.... (idle for 18mn)
ChanServ sets mode: +o MichaelDaum [07:44]
................... (idle for 1h31mn)
CloudNineWould anyone with some knowledge of Foswiki's capabilities be able to let me know if Foswiki would be a good candidate for a project I'm working on? [09:15]
I'll reiterate details provided from the other morning here, but even if someone could respond in chat later on I'll watch logs for feedback offline. Any feedback is appreciated.
In the simplest of terms, my aim would be to set up a collaborative reference manual that would cover several types of aircraft. I envision having a page template I could set up that features various categories common to those aircraft.
Then, other folks in the organization (that may not have the slightest knowledge of topic markup, hypertext, or the like), could utilize said template page to create new/edit aircraft pages and add information easily under those respective categories.
And that's basically it. And if Foswiki is basically built for such function, would the most practical approach be to use data forms or some other built-in template system?
[09:23]
jastprobably a bit of both
it makes sense to use data forms for things where search/filtering is particularly valuable
[09:32]
CloudNineOh cool, thanks for the reply jast. [09:33]
jastfoswiki has two "types" of templates...
one is for giving initial content for a newly created topic, which is basically something that allows users to take liberties (and, of course, changing these templates has no effect on topics already created)
the other is for customizing the "user interface" of foswiki, and one use case for that is providing a standard header/footer for some of your content, using values from form fields
[09:33]
CloudNineIn the latter case, can those UI templates of sorts be applied to particular webs/topics? Or is it more of such a theming sort of thing? [09:36]
jastit can take a while to wrap your head around, but it's all explained in the reference manual (plus there are some third-party plugins to make some aspects a little easier) and if you need any help, you can always come here or talk to us on the mailing list
it's both, not least because you can use all of Foswiki's macros in these UI templates (the official name is "skin templates')
[09:36]
CloudNineSay, I want to add a category down the road to these aircraft type pages, and want that category to propagate to all existing pages as well? [09:37]
jastand the skin mechanism allows you to use different theming/UI in different webs/topics easily
a category would probably be in the data form definition... so if you update that definition, the category automatically shows up as a choice when editing old topics
[09:37]
CloudNineOkay cool. I'll keep camping the reference manuals. I was just having a hard time getting a picture of how it goes together, particularly since the folks ultimately editing/adding content need a really simple interface for doing so. [09:39]
jastright. once you've defined your forms and templates and such, you can basically hide pretty much all of the complicated bits away, e.g. you can make a button/link that creates a new topic with the correct form and template applied [09:40]
CloudNineI see, I see. [09:41]
jasteasy for me to say, of course, because I've spent a lot of time with Foswiki, but at least I can definitely promise that it can be done ;) [09:41]
CloudNineOut of curiosity, and I'm sure it's mentioned somewhere and I've just gleaned it over while trying to gauge whether or not to commit to an install, but in terms of data storage and whatnot is it all file-based or database backend (MySQL, etc.)? [09:43]
jastit's completely file-based. if you want fast searching, there's a plugin that integrates Foswiki with Apache Solr, and then basically it will keep an optimized index of the data from all the text files
for smallish sites the built in search is usually enough
[09:44]
CloudNinePerfect. Cool! Thanks for the info jast, I appreciate the time. [09:45]
.............. (idle for 1h5mn)
FoswikiOnSlack<nuddlegg> test [10:50]
.... (idle for 19mn)
jastfurious tweaking going on? :) [11:09]
MichaelDaumsorry :) [11:13]
.................................... (idle for 2h55mn)
***ChanServ sets mode: +o Lynnwood [14:08]
...... (idle for 26mn)
ChanServ sets mode: +o cdot [14:34]
.... (idle for 16mn)
zak256 has left [14:50]
.......... (idle for 48mn)
LynnwoodFor some reason, i'm having trouble logging into F.O. today.
ah... i see message now
[15:38]
cdotanyone know why I would get "Encoding name should not be undef" with a newly installed 1.1.9?
n.m., setting {Site}{CharSet} cured it (I thought it defaulted to utf8, guess not)
[15:51]
............... (idle for 1h14mn)
LynnwoodGreetings all - I'm looking for a bit of guidance related to setting up development environment. I've set up "EasyDevelopment" with Vagrant. http://foswiki.org/Development/EasyDevelopment [17:09]
***ChanServ sets mode: +o gac410 [17:09]
LynnwoodAs a next step, I wondering about command to make sure the included git repository is up-to-date.
I know this is really basic stuff... but i'm having to refamiliarize myself with using git.
[17:09]
cdotLynnwood: git pull [17:14]
Lynnwoodthanks [17:15]
...... (idle for 29mn)
gac410cdot, Could you review more cookie related changes in https://github.com/foswiki/distro/commit/7c91e2996d58 This is related to Old parked feature request
https://foswiki.org/Development/ConfigurableCookieNamesAndPaths
I think I want to rush this into master. If you log into trunk.f.o, it breaks the login on f.o
[17:44]
cdotwhat was the last patch to 1.1.x?
ok, yes, patch looks fine, I see what you are doing.
[17:46]
gac410last patch to 1.1.x? [17:48]
cdotit was 1.1.10, just read the release notes [17:49]
gac410I'm confused. Are my cookie changes and 1,1,10 different subjects? [17:50]
cdot, If you are using recent perl, there may still be issues in 1.1.10. I tried to patch most of the issues, but I think I missed some. [17:58]
cdotnot a recent perl at all. In the end the problem was that strikeone was disabled (deliberately) and the 1.1.10 patch has an essential fix for that secnario
viz the Rest.pm still checks validation even when {Validation}{Method} is "none"
your cookie changes and 1.1.10 are unrelated
[18:00]
gac410Ah, Why on earth still installing 1,1.x ... There are still some other "concerns" in that code fixed along the way in the 2.x
Okay good. I was having trouble following the conversation :D
[18:01]
cdotinertia of IT depts. [18:02]
gac410Ah,,, yup that will do it. [18:02]
..... (idle for 24mn)
LynnwoodI'm thinking about working on getting a new version of PublishPlugin published - primarily just to include some of the fixes that have been checked in for some time.
One of the tasks that's I'd appreciate someone with great expertise to review is Tasks.Item14198 ("PublishPlugin fails in Foswiki 2.1.2 while trying to render zones")
[18:26]
FoswikiBothttps://foswiki.org/Tasks/Item14198 [ Item14198: PublishPlugin fails in Foswiki 2.1.2 while trying to render zones ] [18:28]
LynnwoodIt appears to me that this task ended up morphing into some other issues and that the fix for the basic issue have been checked in.
One issue that related to core changes has been spun off as separate task.
[18:29]
gac410y, I'm not really sure. It was a pain to have core changes mixed into an extension task. I missed them
I wrote a little audit perl script that checked every git commit Item** number against the release notes and extension change logs and found the unaccounted for changes.
[18:30]
LynnwoodLooks like perhaps status for this task could be changed to Closed. [18:32]
gac410Only if the PublishPlugin was actually uploade? [18:35]
Lynnwoodyou mean if it's published? [18:35]
gac410:) [18:36]
Lynnwoodok, so close it after publishing. [18:36]
gac410Okay everyone. Going once .. .Going twice... Any updates for Release02x01 Otherwise I'll start building 2.1.3 Beta 2. [18:36]
GithubBot[distro] gac410 pushed 1 new commit to Release02x01: https://git.io/vMNWq
distro/Release02x01 7ff4a12 George Clark: Item13884: xgettext run, no string changes, just an offset
[18:39]
***GithubBot has left [18:39]
FoswikiBothttps://foswiki.org/Tasks/Item13884 [ Item13884: Translation changes for master and Foswiki 2.1 ] [18:39]
GithubBot[distro] gac410 pushed 1 new commit to master: https://git.io/vMNWz
distro/master 913e454 George Clark: Merge branch 'Release02x01'
[18:40]
***GithubBot has left [18:40]
....... (idle for 31mn)
LynnwoodI'm reviewing the process for using BuildContrib to publish a plugin and in particular, I'm interested in hour to generate report of changes since prior publish. [19:11]
gac410take a look at core/tools/check_extensions ... primarily intended for the core/default extensions. But I think it will work. [19:11]
LynnwoodIn Extensions.BuildContrib, I see that the "history" function doesn't work with git. [19:12]
gac410Ah... it needs the prior release to be "tagged"
No idea what the build contrib history function is.
[19:12]
Lynnwoodit use to generate a list of svn checkins [19:13]
gac410git log does that. [19:13]
Lynnwoodok. [19:13]
gac410git log --one-line will make it a simple report.
no oops. check_extensions will not work.
If you know the last commit in the last release, then a git log <somecommithash>..HEAD will give you just the changes since that commit
[19:13]
Lynnwoodok i'll try that.
And then that report (or appropriately reformated) is simply added to the Plugin topic?
[19:15]
gac410well, that report will have lots of duplicates. I usually go back to the task summary ... that's what check_extensions.pl did for you.
It's the list of tasks fixed in the plugin topic, not all the commits it took to get there ;)
I've been trying to make a point of using a "git tag 2.3 -s" to create a gpg signed tag for each plugin release I build, then push --tags to push it upstream
[19:17]
LynnwoodLynnwood is digesting that statement with limited grasp of git... [19:19]
gac410A git "tag" is a "named" point in time/space, So for Foswiki releases, we tag each time we build a release, beta or otherwise.
if you have a distro checkout, do a "git tag" to get the list
[19:20]
Lynnwoodok. so makes sense to treat plugins similarly and create a tag when publishing. [19:21]
gac410right. For plugins, I have just been using a simple numeric tag to match the plugin module version.
with a named tag, if you want to run your checkout on the 2.1,0 release, you can "git checkout FoswikiRelease02x01x00" for ex
very easy to flip around between releases. Soooo much lighter weight than svn and branches that were copies of the entire tree
If you tag -s, then it "signs" the tag, with your gpg key if you have one. That adds some "authenticity" to the codebase at that point in time.
[19:21]
Lynnwoodyou say check_extensions.pl won't work for non-default plugins? [19:26]
gac410It tries to find the last tag. and has the core naming convention baked in righ tnow. [19:26]
Lynnwoodok [19:27]
gac410i'd spend some time on it, but I want to keep going on gettgin Beta2 built and uploaded. [19:28]
Lynnwoodquite alright
would you create a tag for plugin _after_ publishing it?
[19:29]
.... (idle for 17mn)
gac4106 - half dozen. Generally I commit the tag and push it once I'm ready to upload.
and after I've tested the packages built by build.pl release. So I know that the tag will reflect the contents of the build.
building foswiki core is a bit different, because the build updates Foswiki.pm with the built version. So there is always one more commit after the build. So I build (updating the module), commit the change, and then tag.
[19:46]
........ (idle for 36mn)
GithubBot[distro] gac410 pushed 1 new commit to Release02x01: https://git.io/vMNKg
distro/Release02x01 f70ed51 George Clark: Item13883: Update copyright, and add to index.html
[20:24]
***GithubBot has left [20:24]
FoswikiBothttps://foswiki.org/Tasks/Item13883 [ Item13883: Documentation changes for master and 2.1 ] [20:24]
..... (idle for 22mn)
LynnwoodBack again on subject of publishing new version of Publish Plugin... I'd welcome opinions about next release number. Even though there have not been that many changes since the last version (2.4.0), i'm tempted to set this as 2.5.0 because the significant change (and reason for publishing new version) is that it works with Foswiki 2+. [20:46]
gac410Please convert to 2-digit decimal revisions. ie. 2.50 instead of 2.5.0 Helps with older sites with ancient perl [20:47]
Lynnwoodok [20:47]
gac410so VERSION a simple decimal. and RELEASE is better as a date '24 Jan 2017' [20:48]
Lynnwoodthat was the next thing i was going to ask [20:48]
gac410Update copyrights to 2017 is a nice one to do as well. [20:48]
LynnwoodIn the last version, cdot had "15237 (2012-07-31)" [20:48]
gac410Y, that's the old svn revision. ... can't use that any more. [20:49]
Lynnwoodgot it [20:49]
gac410If there are any of the old $date$ SVN keywords, $REV$ etc... they should go too. though buildcontrib should catch them and complain.
gac410 is ready to apply 2.1.3-Beta2 to foswiki.org. But will hold off a bit
It will screw up more cookies - changes the domain on the FOSWIKIPREFS and UPDATES plugin cookies
[20:49]
LynnwoodAt what point does the PackageForm get attached to a plugin? is that does as part of build contrib or does it need to be added prior to publishing?
The version of System/PublishPlugin in git doesn't have it and copyright info is listed separated.
[20:56]
gac410when you run the perl build.pl upload, it should download the existing package form, and attach it to the uploaded file
package form is never checked into git.
[20:57]
Lynnwoodok [20:57]
GithubBot[distro] gac410 pushed 1 new commit to Release02x01: https://git.io/vMNDQ
distro/Release02x01 ad08e87 George Clark: Item000: Build 2.1.3 Beta2
[21:01]
***GithubBot has left [21:01]
FoswikiBothttps://foswiki.org/Tasks/Item000 [ Item000 ] [21:01]
Lynnwoodhmmm. just looking at another plugin to see how version, copyright, etc are handled and in this case I see Micha did include PackageForm in git. https://github.com/foswiki/MetaCommentPlugin/blob/master/data/System/MetaCommentPlugin.txt
Looking at a few of his, I guess he does.
[21:06]
gac410hm let me go check. [21:08]
LynnwoodI've taken a look at several of his and they all do. [21:08]
gac410no you are right, I was mistaken. All the core extensions do as welll, :( [21:09]
Lynnwoodok. at least i can make sense of that. [21:09]
gac410I am pretty sure that the buildcontrib does download and recover any existing form and attach it to the upload. [21:10]
LynnwoodDo you think i should create a task for preparing the plugin for publishing? (so i have something to reference the checkins for updates to docs and such) [21:11]
gac410For plugins, I usually just pick one of the tasks to use [21:11]
Lynnwoodok
i'll use the most recent
[21:11]
gac410We have enough noise in the tasks web, no need to create extra tasks to release other tasks [21:12]
Lynnwoodagreed. I'm just needing to get back up to speed and don't want to contribute to mess. Thanks for answering all my questions! [21:13]
gac410sure... glad to help - even the wrong answers are free ... [21:16]
........ (idle for 38mn)
LynnwoodI just tried pushing my commits to PublishPlugin but failed.
I thought I had commit access but guess not...
[21:54]
gac410what did it fail with
hang on I'll check. What's your github id
[21:55]
LynnwoodPermission to foswiki/PublishPlugin.git denied to Lynnwood. [21:55]
gac410I just sent that ID an invite.
I'll add you to the Core developers group once you confirm the invite That should give you access to everything pretty much
[21:57]
Lynnwoodok
don't need no big knives...
all done. thanks
[21:58]
gac410Okay you are all set in Core Developers group - That should give you commit access. [22:02]
GithubBot[PublishPlugin] Lynnwood pushed 1 new commit to master: https://git.io/vMNbd
PublishPlugin/master a10596f Lynnwood Brown: Item14198: Update plugin info for new release.
[22:02]
***GithubBot has left [22:02]
FoswikiBothttps://foswiki.org/Tasks/Item14198 [ Item14198: PublishPlugin fails in Foswiki 2.1.2 while trying to render zones ] [22:02]
Lynnwoodsure enough... it worked [22:02]
gac410cool [22:02]
Lynnwoodi've got to got pick up kids. I'm going to complete publishing new release of PublishPlugin tonight or in morning. [22:03]
gac410okay sounds good. Once evening rolls aroudn I get 2.1.3 Beta2 on the f.o site. Then we'll be able to enable the new blog [22:03]
Lynnwoodgreat! [22:03]
gac410Installed as a web on f.o but uses NatSkin and all the bells and whistles Getting the cookie sharing so it just looks lilke another web was the biggest challenge. [22:04]
Lynnwood: just a suggestion - we normally override plugin topic author fields, to ProjectContributor, so sites without that user don't have broken links.
Oh.. maybe my mistake, but you have VERSION and RELEASE backwards. VERSION is a formal perl module version, so a decimal number RELEASE is the free-form where we suggest the date.
That might cause configure to croak, as it tries to compare VERSION strings with either a numeric compare, or using the perl version-> object methods to handle the dotted-decimal triplet versions.
[22:18]
Anyway Lynnwood I left a comment on the commit so you'll get an email Also as a hint, if you use Foswikitask:ItemNNNN format, then interwikiplugin should link them. [22:32]
Lynnwoodgot email. thanks for checking it! sorry for stupid errors. I'll fix it all a little later.
gone again...
[22:46]
gac410 - Your comment regarding "Foswikitask:ItemNNNN" - is that for the message on the commit? [22:58]
gac410no ... in the change log in the topic. No big deal. Just look at one of the core extensions like ConfigurePlugin.txt [23:09]
.... (idle for 18mn)
some devs use the format in the topic change history, others don't bother. not really consistent. Your commits were just fine. [23:27]

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