Question

I am running 4.01 with Apache and mod_perl. The problem is that when I click the edit button for a EditTable and click save, the headers are replaced with names of a previously edited table. (This breaks XpTrackerPlugin) I highly suspect mod_perl, but I'm not sure what to do about it.

Any ideas on what I should change?

Environment

-- JoelOnofrio - 22 Feb 2006

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

Hello, I had exactly the same problem after installing the EditTablePlugin enhancements. The work around was to include "| |" after the edittable definition or column headers. I suppose Twiki assumes there is a table there with data so doesnt overwrite your code.

-- JamesBarker - 22 Feb 2006

Thanks for the comment, but I'm not sure how where to put the vertical bars.

Here are the two tables. The steps to reproduce are:

1. Create two pages with one of the following tables on each:

2. Use the edit button to edit a table on one page

3. Go to the other page and edit.

Result: The second page edited has the row headers of the other table. (i.e. Summary, Team, etc...)

-- JoelOnofrio - 22 Feb 2006

That could be an issue with mod_perl. Did you try if the bug happens when mod_perl is disabled?

-- PeterThoeny - 22 Feb 2006

I haven't tried yet but I debugged a bit and it looks like the handleTableRows in Core.pm gets passed the correct table headers when you click edit, but when you click save the header passed to handleTableRows are incorrect.

-- JoelOnofrio - 23 Feb 2006

As a workaround, try to exclude mod_perl from edit and save (run the performance critical view, viewauth, rdiff and rdiffauth under mod_perl

-- PeterThoeny - 12 Mar 2006

Or may be not, see mod_perl note at SettingLibPath dated 11 Mar 2006.

-- PeterThoeny - 13 Mar 2006

Thanks Peter. I'm a bit confused though by the SettingLibPath you mentioned. It sounds like there is nothing I can do...

-- JoelOnofrio - 22 Mar 2006

Seems like this Plugin does not work well under mod_perl.

-- PeterThoeny - 01 May 2006

We have the same problem at my company. That's really annoying as we now have a lot people using that plug-in in various TWiki applications. I have to try to reproduce with and without mod_perl. I understand there is no fix for that problem other than disabling mod_perl.

-- StephaneLenclud - 17 Dec 2006

Are there any new ideas how to solve this problem?

-- AlexRaabe - 23 Mar 2007

Presumably, it requires a developer to fix the plugin so that it is mod_perl safe.

-- SvenDowideit - 28 Apr 2007

Tracked in Bugs:Item3993.

-- PeterThoeny - 28 Apr 2007

I think that I'm having this same problem on read only columns. What seems to fix it for me is forcing it to ALWAYS read the original topic on read only columns.

In Core.pm around line 500 there is an unless( defined $table) loop, I just turned it to unless(0).

This is sub optimal, but at least this way I FORCE it always read the old topic fresh every time, as I am guessing that mod_perl keeps the old data around despite being in different topics.

-- MosheHyzon - 25 Oct 2007