professor99
Forum Replies Created
-
This is a known problem with WordPress 3.5.1. Discussion and fixes here. Fixed in latest development version.
Try the latest development version.
If your using WordPress 3.5.1 this is a known problem. More discussion and fixes here. Fixed in the development version
All fixed in the development version
Try the development version. It already has this.
Just updated the development fork with the right version number 1.1.0-fork-2RRR-4.3. If you installed 4.3 already don’t worry too much as the only effect if you don’t reload the release is that it will display as 1.1.0-fork-2RRR-4.2 otherwise
Hi Jonga1306,
You probably have updated fine as I just checked my support page and found my version number is still 4.2. So congratulations for finding the first bug. I have two cans of insecticide in front of me as I type and are in a dilemma as to which one to use :).
As to your dilemma in order to further define the problem try doing the following.
1. Disable all plugins including s2member
2. Clean out the cache of your browser just in case an old javascript file is causing the problem
Try uploading as admin using the following three methods (you did mention some of this above but just making sure).
3. Featured image upload.
4. Editor ‘Insert Media’ upload
5. Attachment upload (using the Frontend attachment field)6. Can you use insert an image already in the media library without problems for methods 1 and 2?
7. Just in case it’s a WordPress problem try doing an upload from the backend admin Media Library page.
Hi ninofrenn,
Your right about gpspake’s code but wrong about the development release. It applies wordpress defaults on the server side as well.
Hi Handoko,
The main branch will be updated once we have determined what features to leave in or out. We are also looking at a Pro version of Frontend that enables extreme customization via a new interface.
There have been two reasons we have kept the three forks separate for now. Firstly all were undergoing extreme development concentrating on different parts of Frontend. Secondly we are making sure the forks works in the majority of cases (hence my forks alpha status).
Once we get over the WordPress 3.5 problems and the addition of a preview button my fork will probably will go beta.
As I state in the Readme not all features of the fork will go in the main branch as some are specific to my app and may not be appropriate for everybody.
So which one to use?
If the official release version does the job and you want an easy upgrade channel it’s the one to go for.
If you love the features in the fork and cant live without them go for it.
If you need much the same with multiple forms gpsake has an interesting fork.
If you need multiple forms and/or the ability to customize everything wait another week or two for Tareq’s PRO version.
Hi qzha017,
I actually haven’t looked at the post expirator although I added the expiry time to the edit post form.
However if as you say it simply changes the post status to draft could you can achieve the same effect by using the edit post form and putting in a new expiry time and changing the newly added post status field to publish?
Hi Jonga,
My new development version 4.3 passed my remaining tests in no time and is now released. Give it a try to see if it solves your problems.
Hi WPChina.
Have added the Slug field to the new development release 4.3.
The new development version 4.3 I have now released fixes now enables Frontend to work with the default WordPress permalinks and fixes the problems above
Just landed the new development version 4.3 which includes these fixes
The next release of this development fork 4.3 is now available.
This update adds a Slug and Post Status fields and fixes some bugs.
Notably it enables frontend to work with the default WordPresss permalinks which only include page ids.It also fixes a few bugs with attachment and images uploads (particulary with WordPress 3.5.1) and now links these properly with there parent post rather than being ‘unattached’ in the Media Library.
This hasn’t yet been extensively tested on Internet Explorer 9 & 10 and I would be grateful if someone could test this especially with the WordPress 2010 and 2011 themes.
There are other minor changes as well which are listed in the README at the following link
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_3/README_2RRR_4_3.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_3/screenshot_top_2RRR_3_0.png
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_3/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 XPBug 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_3/wp-user-frontend_1_1_2RRR_4_3_alpha.zip
A Github repository is available at the following link
https://github.com/professor99/WP-User-Frontend/tree/2RRR
NEW INSTALL INSTRUCTIONS
This development version unlike the previous ones is a complete version of WPUF. If you already have WPUF installed move it’s directory out of the WordPress plugin directory it case you want to reinstall it (Note the downgrade instructions in the ReadMe).
Then install as a normal WordPress plugin. Simply unzip it and copy the wp-user-frontend directory to the WordPress plugin directory.
Activate it and Presto!
Cheers
TheProfessor
