The next release of this development fork is now available. This version adds Ajax form style updates and better error and info messages. It also adds a redirect option for Add/Edit Post pages and the ability to filter options. There are lots of other changes as well including bug fixes plus visual changes to buttons and attachments for the Add/Edit Post pages.
Here’s a link to a screenshot of the Edit Post Page.
And here’s the readme
[ Moderator note: Backticks inserted, you really don’t need to post that here. A link would have sufficed. ]
README WP User Frontend Version: 1.1-fork-2RRR-2.0 alpha
========================================================
Modified Code: Andy Bruin (professor99)
Original Code: Tareq Hassan (tareq1988)
Introduction
-------------
This is a fork from WP User Frontend Version 1.1.
It is a major update of WP User Frontend concentrating on useability and customerisation.
It focuses on Add Post and Edit Post functionality.
There are some bug fixes included as well.
This version adds Ajax form style updates and better error and info messages.
It also adds the ability to filter options.
There are some additional bug fixes included as well.
Some of these changes are outlined by the following items on the WP User Frontend support forum.
http://wordpress.org/support/topic/custom-editors
http://wordpress.org/support/topic/plugin-wp-user-frontend-redirecting-after-posting
http://wordpress.org/support/topic/allow-to-choose-category-filter
http://wordpress.org/support/topic/close-button-and-return-on-post
http://wordpress.org/support/topic/security-problem-doesnt-observe-user-capabilities
Status
------
This code is ALPHA! Use it at you own risk!
It currently has only been tested in the following configuration.
Wordpress 3.4.2
Firefox 16.0.2
IBM PC
This code is a public development fork of WP User Frontend.
It is not written by or supported by the author of WP User Frontend (Tareq Hasan).
Also is not an official release of WP User Frontend.
So please be aware this code may not be included in the next official release of WP User Frontend.
Bugs
-----
Please report bugs via this special topic on the WP User FrontEnd forum
http://wordpress.org/support/topic/frontend-updates-2rrr-fork
Please report only bugs here.
All suggestions for updates to WP User Frontend need to go to the normal support forum.
http://wordpress.org/support/plugin/wp-user-frontend
Download
--------
http://2rrr.org.au/downloads/wp-user-frontend/wp-user-frontend_1_1_2RRR_2_0_alpha.zip
A Github repository is availiable
https://github.com/professor99/WP-User-Frontend
Examples
---------
Examples of use are provided in the directory /examples.
AddPost Shortcodes
--------------------
Shortcode examples::
[wpuf_addpost]
[wpuf_addpost close="false"]
[wpuf_addpost close="false" redirect="none"]
Shortcode options:
post_type: post | <otherPostType>
post: (default)
<otherPostType>: other post types
close: true | false
true: will display close button and redirect to last page on close (default)
false:
redirect: none | auto | current | new | last
none: do nothing
auto: If close==true will load last page on post.
Else will reload current page on post. (default)
current: will reload current page on post
new: will load new page on post
last: will load last page on post
EditPost Shortcodes
------------------
Shortcode examples::
[wpuf_editpost]
[wpuf_editpost close="false"]
[wpuf_editpost close="false" redirect="none"]
Shortcode options:
close: true | false
true: will display close button and redirect to last page on close (default)
false:
redirect: none | auto | current | new | last
none: do nothing
auto: If close==true will load last page on post.
Else will reload current page on post. (default)
current: will reload current page on post
new: will load new page on post
last: will load last page on post
Installation
------------
This update requires the pre-installation of WP User FrontEnd version 1.1.
If you have another version of WP User Front End installed this update will not work.
Changed code is in /wp-user-frontend in the same directory structure as the original files.
Before using make a copy of your original files for safe keeping just in case something breaks.
Then copy the files across.
Changelog
---------
= 1.1-fork-2RRR-2.0 professor99 =
* Now uses jquery.form to do Ajax style updates.
* Post redirect shortcut option added.
* Better info and error messages.
* Suppress "edit_post_link" on WP User Frontend pages
* Added wpuf_get_option filter
* Removed wpuf_allow_cats filter
* Re-styled buttons
* Re-styled attachment display
* Added wpuf prefix to some css classes
= 1.1-fork-2RRR-1.0 professor99 =
* Custom editor option added.
* Editors use max availiable width.
* Close button added as shortcut option and redirects set to suit.
* wpuf_allow_cats filter added.
* Security checks updated.
* Code updated to allow use of wpuf_can_post filter for non logged in users.
Last word
---------
Hope you find this useful. Please report bugs as mentioned above.
Big thanks to Tareq Hasan for his work putting together WP User Frontend.
Cheers
TheProfessor
Bugfix for servers where PHP version < 5.3
Download here
Big thanks to Carlos-Vazquez for reporting this. Can you re-test?
Cheers
TheProfessor
The next release of this development fork 3.0 is now available.
This hasn’t yet been tested on Internet Explorer 9 & 10 and I would be grateful if someone could test this especially with the WordPress 2010 and 2011 themes.
The main differences from 1.1-fork-2RRR-2.1 follow:
– Optionally add Excerpts to the Add/Edit Post forms.
– Add/Edit Post forms re-styled to suit excerpts.
– Publish and expiration times can now be edited on the Edit Post form.
– A Delete button can be optionally added to the Edit Post Form.
– Attachment/Featured Image buttons fixed for Flash/Silverlight.
– CSS has been strengthened for use in other themes.
– CSS has been rearranged and formatted for readability.
– CSS has been tested and fixed for popular browsers using 2010/2011 WordPress themes.
Other changes are listed in the README at the following link
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_3_0/README_2RRR_3_0.txt
Screenshots for the edit page can be found at the following links
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_3_0/screenshot_top_2RRR_3_0.png
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_3_0/screenshot_bottom_2RRR_3_0.png
It currently has only been tested in the following configurations.
WordPress 3.4.2
Apache Server
PHP 5.2 & 5.3
WordPress 2010 Theme
WordPress 2011 Theme
Firefox 16.0.2
Safari 5.0.533.16 (should work 4.1+)
Chrome 23.0.1271.95m (should work 5.0+)
Internet Explorer 7.0 & 8.0
Windows XP
Bug Reports for other configurations would be greatly appreciated.
The update can be downloaded at the following link
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_3_0/wp-user-frontend_1_1_2RRR_3_0_alpha.zip
A Github repository is available at the following link
https://github.com/professor99/WP-User-Frontend/tree/2RRR
Cheers
TheProfessor
Good work – Hope you merge with the original too.
Just tested your fork with IE8. It has some issues, But I’ve found some fixes. You can get attachments working in IE8, if you remove silverlight from the runtimes on line 50 of your attachment.php
The next issue I’m working for is the upload progress percentage is not showing while uploading a file in IE8….
Thanks heaps Runamok for testing this.
Ive tried this on my install without problems with attachment.php set to use only silverlight so it may be a compatabilty problem. Below is my standard help message with my configuration. Post me back on this email address (abruinATihugDOTcomDOTau with your configuration. Also see if flash has the same problem. I also noticed in other posts that you had similar problems with previous versions of frontend as well. PS It would be great if you could tried this updated version of Frontend on your IE9 machine as well.
Thanks TheProfessor
Add Your Info (myinfo)
Server
——-
WordPress Version (3.4.2)
Apache Version (2.2.22)
PHP Version (5.2,5.3)
MySQL version (5.1.65)
Versions of all other installed WordPress plugins.
error messages
Client
——–
Platform (IBM PC/MAC etc) – (IBM PC)
Browser Version (IE7, IE8)
error messages
Whoops, forgot to include the Silverlght plugin version.
Mines 4.1.10329.0
hello… I want to share this too…
http://reigelgallarde.me/programming/wp-user-frontend-multiple-forms/
also, I was thinking if we could use the wp native attachment api… I have not researched about it yet, but I think that would be better.
Professor99,
I believe I have this resolved. My webserver (IIS6) did not have the silverlight mimetypes registered of the box. This caused me to think silverlight was broken and explains why I resorted to stripping out silverlight in order to force flash on IE. My webserver didn’t recognize or want to serve files with a silverlight file extension. After I registered the silverlight mimetypes on IIS6.0 everything seems to work!
Here is some info on my setup. The PHP/MySQL versions are from the Microsoft WebPI 4 installer. WP is updated to 3.5
Server
——-
WordPress Version (3.5)
IIS Version (6.0) (+silverlight mimetypes)
PHP Version (5.3.18)
MySQL version (5.1.66-community)
Client
——–
Platform (Windows 7 Enterprise x64)
Browser Version (IE8 reset to defaults)
Another IE8 tip. Compatibility mode will break the plugin.
Hope this helps another soul who may be following in my footsteps!
Thanks Reigel for mentioning http://reigelgallarde.me/programming/wp-user-frontend-multiple-forms/. It certainly looks interesting. Tareq mentioned to me earlier that he was thinking about something like this and I was not so sure of the possibilities till I saw your YouTube video.
If you are interested in forking my development version on GitHub and adding your code I got one more update in the works which should be published by the end of this week. This is mostly a security update just to make FrontEnd conform with WordPress Roles and Capabilities and tighten up some areas. After this is done it would be great if we can integrate both for development purposes.
Tareq has mentioned he is thinking of updating his code to do much the same but implemented in a different manner. However he is currently time limited because of work commitments and this could be a while in the making. However he is quite impressed with that others such as us are making such efforts to improve FrontEnd.
Hi Runamok81
Thanks heaps for this info.
I haven’t yet updated to WordPress 3.5 so this is great news. Also knowing it works on IIS6 is a help.
I’m intrigued that you mentioned it doesn’t work with IE8 compatibility mode. I gather you mean “Compatibility View” which makes IE8 emulate IE7. This works fine for the website I am currently developing and I did test this extensively with the WordPress 2010/2011 themes. Could you please send me details of how it breaks. Extra details such as the WordPress Theme you are using and the DOCTYPE of the webpages it breaks on would be useful.
Also did you get a chance to test it on IE9?
Thanks
The Professor
The next release of this development fork 4.0 is now available.
This update sets WP User Frontend default edit/add/delete post permissions to WordPress defaults. Old installations retain previous settings.
This hasn’t yet been tested on Internet Explorer 9 & 10 and I would be grateful if someone could test this especially with the WordPress 2010 and 2011 themes.
The main differences from 1.1-fork-2RRR-3.0 follow:
* Added “Users can post?” option.
* Added “default” parameter for “Users can edit post?” option.
* Added “default” parameter for “Users can delete post?” option.
* Added “default” parameter for “Post Status” option.
* Added version to support option page.
* Added Downgrade menu
* Better language support for info div
* Enhanced security
* Added $post_type parameter to wpuf_can_post filter.
* Added $post_id parameter to wpuf_can_edit filter.
* Added wpuf_can_delete filter
Other changes are listed in the README at the following link
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_0/README_2RRR_4_0.txt
Screenshots for the edit page can be found at the following links (Same as 3.0)
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_0/screenshot_top_2RRR_4_0.png
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_0/screenshot_bottom_2RRR_4_0.png
It currently has only been tested in the following configurations.
WordPress 3.4.2
Apache Server
PHP 5.2 & 5.3
WordPress 2010 Theme
WordPress 2011 Theme
Firefox 16.0.2
Safari 5.0.533.16 (should work 4.1+)
Chrome 23.0.1271.95m (should work 5.0+)
Internet Explorer 7.0 & 8.0
Windows XP
Bug Reports for other configurations would be greatly appreciated.
The update can be downloaded at the following link
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_0/wp-user-frontend_1_1_2RRR_4_0_alpha.zip
A Github repository is available at the following link
https://github.com/professor99/WP-User-Frontend/tree/2RRR
Cheers
TheProfessor
Hey TheProfessor. Thanks for the update. Not sure if it’s got what I need in it and with testing I’ve found an issue…
* Issue 1 – When I used to submit a post it would confirm and I can’t rememeber if it went to the dashboard then, or cleared the add post form, but now (even though it IS submitting the post) it just sits there and says ‘Please wait…’
What I’m needing/trying to do/having issues with…
1. Admin user accounts can add a post and include a youtube embed code, but any other user type cannot?
2. Admin, Editor & Author user accounts show the upload/insert for images, etc. above the Description area… Contributors does not show this?
Any thoughts or ideas would be greatly appreciated.
~ Justin
Thanks justinwhedon for testing this.
Issue1
======
Need to know a few things more about Issue 1.
1. Are you referring to a previous development fork update or the official 1.1 version when you refer to past behaviour?
2. Please check to see if the submitted post got submitted to the database despite the continuous “Please Wait” .
3. See if Edit Post has the same behavior as Add Post on post submission
4. Do the delete/close buttons work?
Can you provide me with these following details
Server
——-
WordPress Version
PHP Version
error messages
Client
——–
Platform (IBM PC/MAC etc)
Browser Version
error messages (Firefox – Firebug Console Messages?)
Other Issues
============
1. Admin user accounts can add a post and include a youtube embed code, but any other user type cannot?
Need to know more on how you do this
2. Admin, Editor & Author user accounts show the upload/insert for images, etc. above the Description area… Contributors does not show this?
This is a WordPress editor default as contributors (or subscibers) don’t have the “upload_files” capability. See http://codex.wordpress.org/Roles_and_Capabilities for more info. You may be able to change this by using the following function http://codex.wordpress.org/Function_Reference/add_cap appropriately in your themes functions.php file
Professor… thanks so much for the quick reply… I’ll try to answer as best as I can but if I leave anything out I’ll try to post those later on tonight if possible.
——————————————————————–
1. Are you referring to a previous development fork update or the official 1.1 version when you refer to past behaviour?
Official 1.1 version
2. Please check to see if the submitted post got submitted to the database despite the continuous “Please Wait” .
The submitted post DOES get submitted to the database.
3. See if Edit Post has the same behavior as Add Post on post submission
4. Do the delete/close buttons work?
I’ll have to answer this later
Can you provide me with these following details
Server: Linux (GoDaddy)
——-
WordPress Version: 3.3.2
PHP Version: 5.2
Client
——–
Platform (IBM PC/MAC etc)
Browser Version – Mac FF & Chrome (sorry, not sure what versions as I’m not at home)
============
1. Admin user accounts can add a post and include a youtube embed code, but any other user type cannot?
Basically any ‘user type’ except Admin. If I use the Front End to publish a post. You go to YouTube, choose share, embed and it gives you an iFrame snippet of code…
<iframe width="560" height="315" src="http://www.youtube.com/embed/cKZStlBECHo" frameborder="0" allowfullscreen></iframe>
If I put that in the description (HTML) and publish it will completely disappear as if it was never there… unless it’s an Admin account then it posts fine.
I hope that answers enough… if you need more info please et me know… Again, thank you so much.
