EditThisPagePHP Wishlist
Is there a feature you'd like to see in EdithThisPagePHP? If you can't live without it, there's probably someone else that can't either. Add a note here to tell us about it. (Click the '+' symbol near the bottom of the page to access the comment form). We can't promise anything, but frequently requested features do get bumped up the priority list.
Wishlist
- The title values for the two RSS feeds should be different.
Changed in 0.5b3 -
We should make the output of the tokens consistent as far as they break. For
instance, right now in
http://editthispagephp.sourceforge.net/demo_05b2/index.php :
Trackbacks and Comments:__HIDDEN_ AREA_BUTTON__
Edit Button: __ EDIT_BUTTON__
...break differently, even though both are buttons.
Changed in 0.5b3. - Just ran into this one when posting the above entry - some way of escaping tokens so you can include them as regular text
- Maybe some alternative buttons, that work the same, but have different looks:
__HIDDEN_AREA_BUTTON_ALT_2__
__EDIT_BUTTON_ALT_2__
Or maybe different themes.
Added two new tokens in 0.5b3:
_ _HIDDEN_AREA_BUTTON_STYLE=BLUEBUTTON_ _
and
_ _EDIT_BUTTON_STYLE=BLUEBUTTON_ _. Please see the INSTALL file. -
Persistence in hidden area openness, probably with a javascript cookie. If it
was open before, when you come back to it then it should stay open. (dwayneh: I'd like to second this one - it's very annoying when you're adding a comment in a hidden area to come back and have the area closed)
Added in 0.5b3 -
ping for blogs.com, blo.gs, technorati, etc. on version changes.
Added in 0.5b3 - more "sell" in the read me and docs, i.e. emphasize more what is useful, valuable, and different about ETP.
-
Another one I noticed when posting this - previewing deactivates the Submit Changes button. Not quite sure how to get around this one yet.
Changed in 0.5b3 - Ability to parse through the HTML, look for new links that didn't exist before, go to those pages and see if they have trackbacks, and if they do, send them, but never do so redundantly.
- Better differentiation and naming between sending trackbacks, recieved trackbacks, and pinging services like blog.com, blog.gs, and technorati.
- Use N or M-dash instead of smaller hyphen for HIDDEN_AREA_BUTTON in open form.
Changed in 0.5b3 - Button to tidy HTML.
Added in 0.5b3 - It would be useful to have an alternative "hide/show" tag that displayed the total number of comments and trackbacks, ala Confluence's Wiki.
If you wish to add items to this wishlist, use the comments feature below:
+
Comments
WOuld be great if could interface with Subversion for versioning
Posted by Keith Nelson at 2004-05-14 08:10:02 / PDT
....WYSIWYG Editor :-) ....for the rest of us :-)
Posted by at 2004-06-01 11:26:41 / PDT
Would like to be able to limit editing of a page to a particular group or individual.
Posted by Mark at 2004-06-02 19:35:14 / PDT
The current version supports the ability to create a number of different groups, each with different permissions.
Posted by Christopher Allen at 2004-06-02 23:41:20 / PDT
I am looking at Wiki-like tools in the perspective of maintaining an intranet. For that purpose WYSIWYG edition and the ability to upload a file to a server store + automatically linking to it are much needed features that I can't find anywhere. But your initiative is definitely going in the right direction. Keep up with it!
Posted by JC Francois at 2004-06-03 09:07:28 / PDT
I've just installed, so I don't have a good deal of feedback. In general, I'm looking for a single tool to replace the wiki and blog we use for internal communication.
Is there a mechanism by which editors can automatically create a new page from within the edit box of another, as one can DoWithWikis? If not, that's my vote for the wish list.
Posted by Steve at 2004-06-21 15:30:27 / PDT
Steve,
Simply rename the current one in the admin interface and delet its content. A new page will be created.
Not really intuitive but easy.
- Lawouach
Posted by Lawouach at 2004-06-25 07:29:20 / PDT
Ah, very good. I assumed rename was mv. But it's cp. That's workable.
Posted by Steve at 2004-06-25 13:04:22 / PDT
just some of the features i'd like to see =)
- be able to completely turn off the rss
- valid (x)html output
- online-editable templates for the comments
- online-editable preferences for page history and diffs
Posted by HVG at 2004-08-08 08:46:07 / PDT
> Simply rename the current one in the admin interface and delet its content. A new page will be created.
> Not really intuitive but easy.
There's another version that's just being wrapped up (should be available Real Soon Now) that adds a Create New Page function. This will create a new page using the same configurations as the current one, but with the default data file. Agreed that the rename page feature isn't exactly intiutive for this. As someone else noted, it should probably be called "Copy page", to better convey cp vs. mv.
It's also going to incorporate a web based installer, so hopefully getting up and running with it will be a little less painful.
WYSYWIG is another thing that's been looked at - basically, there aren't any good, currently maintained WYSIWIG editors out there that are compliant with the BSD license on ETP. If would care to recommend one, that would be great.
(We did recently look at htmlArea, and someone was kind enough to send a patch in incorporating it. We chose not to integrate it because the project seems to have been languishing for some time. The cross-browser version seems to have been sitting in beta for quite awhile).
Requirements would be IE6/Gecko compatibility, and that it produce XHTML1.0 compliant code.
There are plans to give the interface a good work-over. The current one was a quick hack to improve on the very early versions, and make additional features available. Any feedback on what you'd like to see in the UI would be greatly appreciated.
Thanks all for your feedback! It's nice to know that ETP is seeing use.
Posted by Dwayne at 2004-08-09 10:51:20 / PDT
I'm using this script with another language, turkish. I've no problems when I'm reading the text but when I press edit I've a bunch of unreadable characters in the "Body Content" form. I can't edit the previously typed text without decoding those "ı"s. Yet when I hit submit the page everything on the main page is legible again. Where should I tweak the code inorder to make the edit page read those characters?
thanks
Posted by c at 2004-09-07 18:50:49 / PDT
Hi, C,
That sounds like a character set issue. I don't have as much experience I'd like with international charactersets as I'd like, to be honest, but this may work. On line 3845, change the charset to "iso-8859-9", used for the Turkish language. (Alternatively, you could remove this line entirely. It's not strictly correct from a w3c standpoint, but I just noticed that that line isn't present in the public side of the content, so if that's working fine, removing this line may do the trick).
You'll also want to change line 462, in the configuration section for the RSS feed, to "tur", the ISO language code for Turkish.
If that works for you, it would be great if you could drop a note here.
Thanks,
Dwayne
Posted by Dwayne at 2004-09-09 09:42:37 / PDT
testing 0.5b3 upgrade
Posted by dwayneh at 2004-11-11 15:48:09 / PST
Love the easy deployment. The number 1 feature I'd look for is something similar to the image uploading feature but for other types of files (i.e. PDFs and Word docs). That'd really hit the sweet spot.
Cheers,
Dan
Posted by Dan at 2004-12-03 09:32:40 / PST
> Love the easy deployment.
Thanks ;)
> The number 1 feature I'd look for is
> something similar to the image
> uploading feature but for other types
> of files (i.e. PDFs and Word docs).
> That'd really hit the sweet spot.
It's actually an artificial restriction, I think a holdover from early versions. The saveImages() function checks the uploaded file's mime-type to make sure it's an image, otherwise it's disallowed.
There's a very good chance this will become a configuration option in a future release.
(If you don't mind hacking the source, you can change this behaviour in the saveImages() function. There's an if statement that checks the files mime-type - you can add your own to the list, or just change the
if ($filetype != "image/pjpeg"....
condition to
if (1) {
to allow any files.
Not exactly what I'd call an optimal method of configuration, but it will work ;)
Posted by Dwayne at 2004-12-03 10:18:33 / PST
Would you be able to use this WYSIWG code? It appears to have a BSD license.
http://kupu.oscom.org/
Posted by Bradley Peters at 2005-01-16 14:53:26 / PST
* support of textile or phpmarkdown in editing a page
* list of pages (so that can be edited, deleted, etc.)
enough so far... :) the idea is good, still limited because users don't know html.
Posted by franco stellin at 2005-02-20 14:21:19 / PST
Great! Thank You!
suggestion:
All the "style" should be outside of "editthispage_index.php" in a single .css-File called "default.css", which is present by default and linked with the line "" in each dokuments header.
Below this line could be a link to a custom stylesheet: ", commented out by default. "custom.css" could be present by default, too and could have same content like "default.css". When comments are removed, "custom.css" becoms active and changes made in "custom.css" will overwrite "default.css" (because it is linked BELOW "default.css").
Posted by Thorsten Ebeling at 2005-08-11 23:52:49 / PDT