Frontend Updates 2RRR Fork

  • professor99

    (@professor99)


    12 years ago

    Hi all,

    The code updates I have been mentioning in various packages are finally to a point where they can be released.

    The Readme follows.

    [ Moderator note: Backticks inserted, you really don’t need to post that here. A link would have sufficed. ]

    README 2RRR 1.0 For WP User Frontend Version: 1.1 fork: 2RRR 1.0 alpha
========================================================

Introduction
------------

This is a fork from WP User Frontend Version 1.1.
It currently only applies to the Add Post and Edit Post functionality on WP User Frontend.
Use of AjaxForm for Ajax style posts is the next step in this project.
It focuses on both useability and ease of customerization.
There are some bug fixes included as well.

Some of these changes are outlined by the following items on the WP User Frontend support forum.

https://www.ads-software.com/support/topic/custom-editors
https://www.ads-software.com/support/topic/plugin-wp-user-frontend-redirecting-after-posting
https://www.ads-software.com/support/topic/allow-to-choose-category-filter
https://www.ads-software.com/support/topic/close-button-and-return-on-post
https://www.ads-software.com/support/topic/security-problem-doesnt-observe-user-capabilities

Changes from WP User Frontend Version 1.1
-----------------------------------------

 * Main Changes from Version 1.1:

 * 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.

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) and 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 

https://www.ads-software.com/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.

https://www.ads-software.com/support/plugin/wp-user-frontend

Download
--------

https://2rrr.org.au/downloads/wp-user-frontend/wp-user-frontend_1_1_2RRR_1_0_alpha.zip

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.

Examples
--------

Examples of use are provided in the directory /examples.

Add Post Shortcodes
-------------------

Shortcode examples::

	[wpuf_addpost]
	[wpuf_addpost close="false"]

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: 

Edit Post Shortcodes
-------------------

Shortcode examples::

	[wpuf_edit]
	[wpuf_edit close="false"]

Shortcode options:

	close: true | false
		true: will display close button and redirect to last page on close (default)
		false: 

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

    https://www.ads-software.com/extend/plugins/wp-user-frontend/

Viewing 15 replies - 31 through 45 (of 134 total)

  • @professor 99
    My site is actually intranet, so no contributor login available. I am satisfied in not using Relevannsi for the moment. Honestly, I do need to continue development so I have made a note to deliver firebug logs at a later point in time.

    @professor 99

    Thanks so much. Still need to try some of the things from your ideas on posting youtube content… will let you know on that for sure. No worries on the featured images pulling from the library at this point.

    ~ Justin

    Actually just using the URL (YouTube) works perfectly!! Thanks so much.

    ~ Justin

    @2RRR & uf Profs: Let me tell you: great stuff at all. With the 4th fork release now it do what’s should do(for me): default wp role settings. feetback from the core system in a splendid way. My theme:mantra, wp 3.5, tested on FF, others @ once if requested. Using normal category selection (not jquery or ajax) It would be a big effort if thats fork going officialized.
    Great teamwork @ all. going on..lp

    Thread Starter professor99

    (@professor99)

    Hi Runamok81,

    It’s a shame it’s on an intranet because heaps of people were experiencing problems with Relevannsi on the current official version although I’m running it on my development version without problems so far. I might be able to solve it with the following info but no guarantees.

    If you can get me the following from Firebug it would be extremely useful: ‘Console’ log and ‘Net’ log.

    To enable the ability to save a ‘Net’ log install the following Firebug extension NetExport and restart Firefox

    After initial Frontend page load do the following in Firebug.

    1. Console messages: Clear then select ‘All’ and ‘Persist’ selected
    2. Net: Clear then select ‘All’ and ‘Persist’ selected

    1. Add your attachments.
    2. Submit post

    Then

    1. Copy console log into a text file
    2. Using the ‘Export’ option on the ‘Net’ bar save the log as a ‘HAR’ file.

    Send both to me at abruinATihugDOTcomDOTau

    Thread Starter professor99

    (@professor99)

    Thanks lowerpower for your info. I would like to know if it works on IE9 and IE10 browsers if possible.

    Thread Starter professor99

    (@professor99)

    The next release of this development fork 4.2 is now available.

    This update adds a post format field to the add/edit posts pages. It also has some bug fixes.

    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-4.0 follow:

    * Adds a “Post Format” field to the edit/add post forms.
    * Bugfix: Changed version to 1.1.0-fork-2RRR-4.2 (eliminates update prompt)
    * Fixed wpuf_edit shortcode typo.
    * Fixed ‘required’ message opacity bug
    * Fixed Jquery $ conflict bug

    Other changes are listed in the README at the following link

    https://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_2/README_2RRR_4_2.txt

    Screenshots for the edit page can be found at the following links (Same as 3.0)

    https://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_2/screenshot_top_2RRR_3_0.png

    https://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_2/screenshot_bottom_2RRR_3_0.png

    It currently has only been tested in the following configurations.

    WordPress 3.4.2 & 3.5
    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

    https://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_2/wp-user-frontend_1_1_2RRR_4_2_alpha.zip

    A Github repository is available at the following link

    https://github.com/professor99/WP-User-Frontend/tree/2RRR

    Cheers
    TheProfessor

    Thread Starter professor99

    (@professor99)

    Update for Runamok81.

    There is a plugin similar to NetExport for the console log https://www.softwareishard.com/blog/consoleexport/. Please use this for the console log output.

    Hi,

    The js fix for “Submit post” doesn’t works when Charge for posting is actived.
    Wp 3.5
    wp-user-frontend_1_1_2RRR_4_2_alpha
    No other plugin
    Nimble theme for Elegant themes
    Regards.

    – wp 3.5
    – version 1.1.0-fork-2RRR-4.2 alpha

    Warning: require_once(/Applications/XAMPP/xamppfiles/htdocs/wordpress/wp-content/plugins/wp-user-frontend/lib/class.settings-api.php) [function.require-once]: failed to open stream: No such file or directory in /Applications/XAMPP/xamppfiles/htdocs/wordpress/wp-content/plugins/wp-user-frontend/wpuf.php on line 41

    Fatal error: require_once() [function.require]: Failed opening required ‘/Applications/XAMPP/xamppfiles/htdocs/wordpress/wp-content/plugins/wp-user-frontend/lib/class.settings-api.php’ (include_path=’.:/Applications/XAMPP/xamppfiles/lib/php:/Applications/XAMPP/xamppfiles/lib/php/pear’) in /Applications/XAMPP/xamppfiles/htdocs/wordpress/wp-content/plugins/wp-user-frontend/wpuf.php on line 41

    Please excuse this silly question, but I’m new to this.

    Is there a way to implement this development version of the plugin on my site ***without overwriting*** the current WPUF plugin I’m using, as it has custom functionality that I need to keep? Can I merge the development version with my current version without overwriting or breaking what I already have?

    Thanks for your help!

    Thread Starter professor99

    (@professor99)

    Thanks gouffy41. I haven’t tested it with the ‘Charge’ option yet so I will follow that up.

    Thread Starter professor99

    (@professor99)

    Hi teresax. That error is commonly generated when the instructions in the readme for installation of the fork haven’t been followed. The fork files need to be copied over the original Frontend installation. See the readme for details.

    Thread Starter professor99

    (@professor99)

    Hi Wombat. It’s unclear in your post to what exactly is customized in your Frontend installation.

    If it’s the code all updates to Frontend (including official versions) involve overwriting files.

    In this case I suggest you use a compare tool such as my favorite KDiff3 to compare your custom code to the original version of Frontend and then merge it with the forked code.

    If your talking only about custom fields the fork only adds a few options to the database and doesn’t change custom fields. However the fork does change the layout as given here and here which may affect the layout of custom fields.

    The Readme gives instructions for both installation and de-installation of this fork. This recommends you keep a copy of the files of the your original plugin. A downgrade option is also included in the fork’s frontend option page to reset a couple of frontend options to sensible defaults on downgrade back to the original version. No database entries other than these are affected.

    Thread Starter professor99

    (@professor99)

    To gouffy41,

    I’ve looked into the javascript code and the problems you were having when Charge for posting is active are unrelated to this bug. You may have your payment options incorrectly set resulting in an error and no return from the submit.

    Have you tried this in the official version of Frontend? If it doesn’t work in the official version create a separate post heading as I have no experience with this area. Also grab Firefox Firebug logs as mentioned in previous posts which may identify what is wrong.

Viewing 15 replies - 31 through 45 (of 134 total)
  • The topic ‘Frontend Updates 2RRR Fork’ is closed to new replies.