Closed (fixed)
Project:
Diff
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
2 Feb 2007 at 02:37 UTC
Updated:
9 Jun 2016 at 23:46 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
moshe weitzman commentedterrific patch. i just made rotzi a maintainer of this module.
committed to 5.0 and HEAD. hopefully someone will make a patch for 4.7.
Comment #2
toemaz commentedI applied the head patch to the 4.7.x version and then tried to solve the errors. Now, it does not complain anymore, but I can't get the 'preview changes' to work. I'm not trained enough to quickly see where the problem comes from. I gave up after 15 min.
Anyway, here is my patch for 4.7.x which needs some work!
Comment #3
rötzi commentedYou missed a change in the forms handling. The button press has to be checked differently in 4.7 than in 5.0.
Try the new patch.
Comment #4
rötzi commentedpatch applied to cvs
Comment #5
toemaz commentedHi rötzi,
Thx for committing this! I've testing it and it seems everything is ok.
Just one remark: I would like to be able to hide the 'preview changes' button.
The solution would be to create an extra access permission or create a setting variable where you can disable it. Or you can hook it into the admin/settings/node form.
I can create a patch for this but what so you think would be the best option?
Comment #6
moshe weitzman commentedthis button is already protected by 'view revisions' permission. if that is not sufficient, i suggest writing a little module which uses hook_form_alter() to hide the button as desired. i don't want many preferences if possible.
Comment #7
toemaz commentedOk, that will work. Thx for th feedback Moshe.
Comment #8
(not verified) commentedComment #9
BioALIEN commentedMoshe, I think toemaz had a valid suggestion. There should be an access control to hide the "Preview changes" button from node edit. Reason is because this button makes it very confusing when editing other modules such as webform. I know my way around Drupal and this module caught me out. So imagine what it can do to other admins who are not so familiar?
Comment #10
BioALIEN commentedGoing to close this again in favour of the newly created thread.
http://drupal.org/node/115411
Comment #11
catchThis is still a valid issue nine years later. If you have a lot of revisions, the page will eventually hit the memory limit or max_execution_time.
Comment #12
catchApparently I didn't read #1, and this was actually committed to 5.0 originally.
That means somewhere between 5.0 and the 8.x branch it's regressed, so closing this as fixed again, will open a new one.
Comment #13
catch#2746069: Needs tests: No pager on revisions listing is the new issue.