professor99
Forum Replies Created
-
To put this plainly in WordPress terms this means you want to be able to change the posts status from ‘draft’ to ‘published’ and vice-a-versa as can be done on the standard WordPress Edit Post admin page.
I agree this functionality could be useful and am looking at implementing it in the development version. May be a week or two before I do this due to other priorities.
In the development version you can use filters and actions to add a custom editor. There is an example included (Showtime) which does exactly what you want.
This is an option in the development version.
Hi wombat86. Try editing the code using the examples above, the notes in Close Button and return on Post and code in the development version to achieve what you want.
I think there was also some mention of this elsewhere in the forums. Do a search for: “WP USer Frontend” “redirect”
As mentioned in other responses Version 4.0 of my development release should of fixed this.
However thanks gpspake for your effort in investigating this. Having this code here is useful for those who want to stay with the official version but want to tighten their security here.
Thanks heaps gpspake for investigating this and publishing the fix.
I think Version 4.0 of my development release should of fixed this.
Hi gpspake,
Thanks heaps for investigating this and publishing the fix.
Version 4.0 of my development release should of fixed this. Could you check if this achieves the same functionality?
Thanks
TheProfessorThe 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 bugOther changes are listed in the README at the following link
http://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)
http://2rrr.org.au/downloads/wp-user-frontend/2RRR_4_2/screenshot_top_2RRR_3_0.png
http://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 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_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
TheProfessorThanks lowerpower for your info. I would like to know if it works on IE9 and IE10 browsers if possible.
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’ selected1. Add your attachments.
2. Submit postThen
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
This is mostly fixed in the development version
Hi adaldesign,
In regards to the error you reported above how did you install the plugin?
(1) Did you copy the files to the directories of the original frontend installation?
(2) Or did you install it as a new frontend installation (ie it’s own directory). This way would probably result in the error you saw.
It’s meant to be installed over the original frontend installation as in (1).
Hi justinwhedon,
Had a look at the media library code and found that it is only usable to add featured images for pre-existing posts (not new posts) in Frontend in WordPress 3.2.4 and below. This is because it requires a pre-existing post. WordPress’s admin post uses auto-drafts for this purpose.
There was some talk on trac on making the media library more usable for frontend posting and indeed WordPress 3.5 does improve Featured Image usability although I’m yet to check the code in this regard.
So the status of this is that I’m not going to do it for WordPress 3.2.4 and below unless I add a Preview facility (which requires auto-drafts). I may add Previews but it is some time off. Even then I may not do it as the current implementation is simple and obvious where Media Library’s Featured Image upload for WordPress 3.2.4 is anything but obvious.
WordPress 3.5 implementation depends on WordPress codebase but due to older WordPress’s being incompatible I probably wont do this for WordPress 3.5 alone.
Note I’m only talking about this development version. Tareq may have other ideas about the official version.
Hi justinwhedon.
Did you try the option of just using the youtube url as mentioned? It seems to be the easiest way. But then again I’m supposing your trying to make life easy for your contributors by letting them do things the old way though it’s potentially risky. Otherwise probably you need to add another capability though I can’t say what. Check if it works for authors and then just look at the differences in capabilities for clues.
The featured image button is only intended to add a new featured image for each post (for everybody allowed to upload images) so this isn’t a contributor specific problem. I don’t see a huge need for using the library here. However it may be consistent and useful to have it given the editor uses it so I will see if it can be easily done.
Thanks Runamok81 for the info. Some other users have been reporting similar problems with attachments and I would like to know more.
I checked out Relevansi and installed it on my website without any problems with Attachments (though I confirmed the jquery$ “Please Wait problem). I’m keeping Relevansi on my site as it’s quite a good search tool and it’s search stats are very useful.
Could you install Firebug on your Firefox browser and check is there is any Javascript errors on pressing “Submit Post”? Also interested in the contents of the returned net message (if any).
Better still if you can give me a contributor login I can look into this more thoroughly. Email me at abruinATihugDOTcomDOTau a link to your add post page and give me a login/password as a user with contributor role (that way all test posts will be given pending status and wont appear on your website). Obviously I will need the Relevanssi plugin enabled to see the problem
