Edgewall Software
Modify

Opened 17 years ago

Closed 17 years ago

Last modified 16 years ago

#4099 closed defect (fixed)

Submit button missing when editting read only wiki pages

Reported by: PBruin Owned by: Jonas Borgström
Priority: normal Milestone: 0.10.1
Component: wiki system Version: 0.10
Severity: major Keywords:
Cc: peter.bruin@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

I have just upgraded my stable 0.10 version from r4050 to r4171
The problem I face is that when I try to edit a read-only wiki page the Preview Submit and Cancel buttons are missing. The same happens when I create a new page and make it read-only and then press Preview. No buttons are visible.

Attachments (2)

faulty page.txt (308 bytes ) - added by PBruin 17 years ago.
html generated for page without footer and buttons with r4145
not read only page.txt (1.4 KB ) - added by PBruin 17 years ago.
html generated for page that is not checked as read only with r4145

Download all attachments as: .zip

Change History (31)

comment:1 by PBruin, 17 years ago

I confirm that reverting back to r4050 resolves the issue

comment:2 by PBruin, 17 years ago

Sorry, I mean r4041, the other one was the trunk version I used before going back to the stable 0.10-stable branch.

comment:3 by PBruin, 17 years ago

I have done some testing, when using r4144 I can still Submit my changes, with r4145 the submit button has gone.

comment:4 by PBruin, 17 years ago

Cc: peter.bruin@… added

Actually, not just the buttons are missing. The whole footer is missing.

by PBruin, 17 years ago

Attachment: faulty page.txt added

html generated for page without footer and buttons with r4145

by PBruin, 17 years ago

Attachment: not read only page.txt added

html generated for page that is not checked as read only with r4145

comment:5 by PBruin, 17 years ago

Milestone: 0.10.1
Severity: normalmajor

I have added two files that contain the same page when I click preview. Once I have the read-only box checked and the other time not. This was tested on 0.10-stable without any plugins or other additions.

comment:6 by Christian Boos, 17 years ago

Milestone: 0.10.10.10.2

Well, it's too late for milestone:0.10.1 which has been released. Can you try again with that released version or at least r4155, to check if the problem is still present with the latest incarnation of the CSRF fix?

comment:7 by Christian Boos, 17 years ago

Ah, wait, it's probably related to r4184, so yes, try again with the released milestone:0.10.1

comment:8 by Jonas Borgström, 17 years ago

Status: newassigned

This was probably fixed by r4184. Either update to the latest 0.10-stable or the 0.10.1 release.

comment:9 by PBruin, 17 years ago

Ok, this fixes it for this test site. However, my main site has the th:wiki:TracBlogPlugin setup and there it is still present. They use the same installation and I have the plugin in the local configuration of that site. Any tips or do I need to take this to Trac-Hacks?

comment:10 by Christian Boos, 17 years ago

Are you sure you have restarted your main site, and does disabling the plugin "fix" the issue?

comment:11 by PBruin, 17 years ago

Both run on the same apache server. These are the two config I used. First one works, then to test I changed back to the second one and the problem is back.

[components]
acct_mgr.* = enabled
tblog.* = disabled
trac.wiki.web_ui.wikimodule = enabled
tracchangelog.* = enabled
tractags.* = enabled
webadmin.* = enabled

[components]
acct_mgr.* = enabled
tblog.* = enabled
trac.wiki.web_ui.wikimodule = disabled
tracchangelog.* = enabled
tractags.* = enabled
webadmin.* = enabled

comment:12 by PBruin, 17 years ago

Resolution: fixed
Status: assignedclosed

Got it. It was due to the th:wiki:TagsPlugin as this had the same problem as was fixed in wiki.cs in r4184. Thanks for your help!

comment:13 by Christian Boos, 17 years ago

It's a bit strange though, as from what you posted in comment:11, the tractags plugin was enabled in both configurations…

comment:14 by PBruin, 17 years ago

Correct. But the wiki module was not disabled. The tags plugin uses its own wiki module to display the tags in the page and on the edit properties as you can see in this file. I have attached the fixed file to the th:wiki:TagsPlugin page for people to use.

comment:15 by Alec Thomas, 17 years ago

I've updated th:wiki:TagsPlugin, thanks for the patch.

comment:16 by byrnejb@…, 17 years ago

Resolution: fixed
Status: closedreopened

We are running trac-0.10.2 as released via the CentOS-4 team and have this problem with read only pages.

comment:17 by byrnejb@…, 17 years ago

Supplemental correction to above. The repository that provided us with the trac-0.10-2 rpm that wee are using is actually found at http://dag.wieers.com/packages/trac/

comment:18 by byrnejb@…, 17 years ago

It has been six weeks since this issue was reopened. Is there any hope of a repair release or a patch to 0.10.2 in the very near future? If not, then how does one revert to an earlier version?

in reply to:  18 comment:19 by Noah Kantrowitz <coderanger@…>, 17 years ago

Replying to byrnejb@harte-lyne.ca:

It has been six weeks since this issue was reopened. Is there any hope of a repair release or a patch to 0.10.2 in the very near future? If not, then how does one revert to an earlier version?

Are you absolutely sure you are using the default wiki module?

in reply to:  18 comment:20 by Tim Hatch, 17 years ago

Also, have you tried upgrading to the trac-0.10.3-1 which is available in that repository you mentioned?

in reply to:  18 comment:21 by Matthew Good, 17 years ago

Keywords: needinfo added; read only buttons wiki removed

Replying to byrnejb@harte-lyne.ca:

It has been six weeks since this issue was reopened. Is there any hope of a repair release or a patch to 0.10.2 in the very near future? If not, then how does one revert to an earlier version?

I've checked the contents of the Trac 0.10.2 RPM and it contains the fix from r4184, so this is most likely due to the use of the th:TagsPlugin as mentioned above. You will need to upgrade this plugin to fix the issue.

comment:22 by byrnejb@…, 17 years ago

I removed TracTags many months ago because I could never get it to work. There is nothing to upgrade and, as far as I can see, nothing in the trac.ini file that references any of trhe TracTags components except a few comments preserving some of the former settings. I have removed these and altered the trac.ini file to conform with the recommendations of the trac project "trac.ini wiki page. Restarting the httpd server following these changes did not correct the problem.

I was unaware that Dag had updated trac to 0.10.3 (on last Wednesday, Dec. 13). I will apply this update directly and see if this fixes the problem.

comment:23 by byrnejb@…, 17 years ago

I have updated to 0.10.3 and restarted the httpd server. The missing submit buttons have not returned for the read-only pages. I can edit, but I cannot save changes. If this is an artifact of the previous tractags plugin then I would really appreciate some guidance as to how to rid myself of all traces of this component.

comment:24 by byrnejb@…, 17 years ago

I decided that perhaps I would try to re-install tractags and see if that cleared the problem. The difficulty I now face is that the link to TracTags given on the plugins wiki page is defunct as is any reasonably discernible variant. Where is the most recent TracTags plugin found?

comment:25 by Noah Kantrowitz <coderanger@…>, 17 years ago

Double check that you do not have any local modifications to the wiki template (possibly in <env>/templates/wiki.cs).

A copy of the tags plugin page can be found here.

comment:26 by byrnejb@…, 17 years ago

Resolution: fixed
Status: reopenedclosed

Yes! That was the problem. The earlier install of TracTags must have modified the wiki.cs because its fingerprints were all over the version I had in templates. Copying over the default version of wiki.cs cured the problem.

comment:27 by Matthew Good, 17 years ago

Keywords: needinfo removed
Milestone: 0.10.1

Ok, good. It looks like the fix for Trac was originally released in 0.10.1.

in reply to:  description comment:28 by anonymous, 17 years ago

Isn't that the whole point of having a readonly page?

comment:29 by anonymous, 16 years ago

I think that a read only page should be editable only by user with a TRAC_ADMIN permission.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.