Item1830: After last update (1.0.6-1) I can't edit pages anymore

I'm using the foswiki's (fosiki) debian repository and since the last update to the version 1.0.6-1, I can't update any page.

I can open the page in "edit mode" and modify its content but after I click in the "Save" button, I'm redirected to the login page (even if I'm already logged) and after filling the authentication form, I came back to the edited page again but without my changes.

-- ArthurFurlan - 15 Jul 2009

Does "raw edit" work correctly?

Which skin are you using?

-- MichaelTempest - 15 Jul 2009

No, it doesn't... I'm using the "nowysiwyg" mode (the same used here).

I'm not sure about that but I think I'm using the "Foswiki/TWiki's default skin". It's a TWiki instance that was "upgraded" (long time ago) to a Foswik one.

-- ArthurFurlan - 15 Jul 2009

Thank you. This means the problem probably lies with the login and authentication mechanisms, and not with the editor. (There have been issues with both.)

What is {Validation}{Method} (an "expert" Security setting in configure) set to?

And do you use LDAP or "short URLs" (e.g. apache rewrite rules) at all?

-- MichaelTempest - 16 Jul 2009

I just saw the patch you attached to Item1766. What is the relationship between this item and 1766, on your system? For example, do you get the "can't edit" problem with the patch you attached to 1766? If so, what happens without the patch?

If {Validation}{Method} is "strikeone", please try setting it to "embedded", at least as an interim measure. (The "embedded" {Validation}{Method} is the same as 1.0.5 used. It is less secure than "strikeone", which is why using "embedded" is not a long-term solution.)

-- MichaelTempest - 16 Jul 2009

The first relathioship is: these bugs started to happen after the last update.

I tought that fixing the bug of the "foswiki_redirect_cache" I'd also fix the other bug but I was wrong. So it seems the bugs have no other relationship... Actually I've the bug at 1766 solved (using the patch) but I still can't edit pages. =/

I was using the "strikeone" {Validation}{Method} and now I switched to "embbeded" but it doesn't solve the problem... I've tried it before with no success.

And yes, I'm using "short URLs"... Should I attach my apache's config?

-- ArthurFurlan - 16 Jul 2009

Yes, please. The apache config will help. I don't think I can add much more here, but I'm changing the status back to new and I'll ask other developers to have a look.

-- MichaelTempest - 17 Jul 2009

mmm, yes, pleae, can you attach the /etc/foswiki/apache.conf and /etc/foswiki/LocalSite.cfg files please?

I think there's a wrong setting in the LocalSite, but its easiest to have a look at both together.

-- SvenDowideit - 18 Jul 2009

Ok, I added all the files[1,2,3]... I also added the /etc/foswiki/apache.conf[1] but you'll see in my apache's config[2] that it's not being used.

[1]. http://foswiki.org/pub/Tasks/Item1830/foswiki-apache.conf

[2]. http://foswiki.org/pub/Tasks/Item1830/mywiki-apache.conf

[3]. http://foswiki.org/pub/Tasks/Item1830/LocalSite.cfg

-- ArthurFurlan - 18 Jul 2009

Just to say that I've fixed a bug in the embedded code checking, that would make it always show the validation page. But it shouldn't show you the login page...

Anyway, can you try the patch in distro:5bb5b172f678 please? I highly doubt it will fix anything, and I'm pretty sure Sven has a good idea of what's wrong, but... just in case...

-- OlivierRaginel - 18 Jul 2009

Just perfect... I added the patch and then all back to work again, thank you guys!

-- ArthurFurlan - 19 Jul 2009

Just a comment... In the next upgrade, please don't remove the previous version of the repository because I tried to downgrade when the problems started but I couldn't find it anywhere.

-- ArthurFurlan - 19 Jul 2009

noted - I think adding --keepunreferencedfiles to my reprepro cmdline is now going to do this

I'll make a 1.0.6-3 with that patch asap (odd that editing is ok on my debian systems, but meh

-- SvenDowideit - 20 Jul 2009

In the next upgrade, please don't remove the previous version of the repository because I tried to downgrade when the problems started but I couldn't find it anywhere.

It is the Sourceforge website upgrade that has goofed up the download areas for many projects.

I have raised the issue from day 1 on the Sourceforge IRC channel and raised a ticket. But the suckers do nothing. I even tried to deactivate the 1.0.5 and reactivate it to revive it. I always keep the previous file release active.

https://sourceforge.net/apps/trac/sourceforge/ticket/2227.

I guess it is time to make some more noise.

-- KennethLavrsen - 20 Jul 2009

This appears to have been confirmed as is being worked on by Sven.

-- CrawfordCurrie - 05 Aug 2009

---

released in 1.0.6-3 debian package, but the real work done by Olivier will be in 1.0.7

-- SvenDowideit - 05 Sep 2009