professor99
Forum Replies Created
-
WordPress does have problems with having two plugins with the same plugin name in it’s plugin directories. What I normally do is move the old plugin to a sub directory of the new plugin. Once this is done try the featured image upload again.
You should always clear the browser’s cache after updating a plugin as often javascript files and stylesheets don’t get updated on page load which can cause all types of weird behavior.
Can’t be done using Frontend currently but the forthcoming Frontend Pro will be able to be customized very easily and we have already considered generating template files from this though that may not be included in the initial release.
Thanks SloGH. I will put that fix in the next development version.
Strange that the development version didn’t reduce this by at least a factor of 50 (As it calls it only once instead of 50 times in Version 1.1). Which development version did you load?
Looks like you changed the theme or the theme styling.
In your screenshot all Frontend elements are there but some buttons have lost their styling and the category list as also lost it’s styling. Each li item has also got a bullet.
Try changing your theme back to 2012 to see if the theme is indeed the cause of your problem.
Hi aesthetic,
The Pro version features easy customization (pretty much everything) and multiple forms. It’s admin interface is very different to the current Frontend version.
The Pro version was about to released but I recommended some changes to Tareq to make it easier to expand on it’s capabilities with future releases so it’s now been slightly delayed.
As far as styling goes the development version is actually tighter than the version 1.1 but pretty much everything can be changed via wpuf.css. I can’t speak for the Pro version but I expect much the same.
The image fix for 3.5.1 was already included in the last development release (4.3).
Actually there’s mainly three of us working on Frontend code (Me, Tareq, and gpspake) although some others are helping too with bits and pieces. We are all collaborating on each others code.
Tareq has a new Pro version coming out soon once he digests my long list of recommendations.
Me and Gpspake have just managed to iron out Frontends problems with the image library in WordPress 3.5.1 which are integrated in the current development version.
The development version will probably go beta once I add a few more bug fixes. Most if not all development features will be integrated in the next official version of frontend.
Sometime down the line we will also be integrating some of Pro’s features into the standard Frontend
Hi Chilyn,
When you say “The featured image still shows full-sized,” I assume from your title you mean only in posts?
If so that is standard behavior for WordPress 3.5.1 for the standard theme 2012 though I don’t know about Wild Community Buddypress theme.
Frontend has the same behavior here as the WordPress rear end editor.
One workaround for you is to maybe to use one of the classes given and add a modified version to your themes style sheet at the end (so it overrides previous definitions). Can’t guarantee this will work and not stuff anything else up but worth a try.
Try
img.wp-post-image{
height: 70px;
width: 70px;
}Lastly I’m interested in this comment “Also, the featured image has to be reset from the admin backend now — it uploads, but does not set. “.
Can you give me more detail about that. For example does the featured image show on the add/edit page?
Cheers
TheProfessorFor the excerpt you need to also enable the “Allow excerpt” option. The “Require excerpt” only makes excerpt user entry compulsory if the “Allow excerpt” option is enabled.
Not sure about your Featured Image problem. Will look into it.
Actually I made a mistake in assuming the above jquery excerpts were hard code rather than html page source (late night).
The jquery files as loaded are normal and don’t look like the source of the problem.
However the 200 and 500 errors are abnormal.
Hi Jonga,
The logs would be quiet useful as often they contain errors that are unreported otherwise.
You can email me them at abruinATihugDOTcomDOTau
Also the ‘Post Status’ field problem reported by loginid has also been found to be a bug.
To fix in the current development version change the following lines in wpuf-edit-post.php in the function submit_post().
//Set post status if ( wpuf_get_option( 'allow_status') == 'on' && $this->logged_in && isset($_POST['wpuf_post_status']) ) { $post_stat = $_POST['wpuf_post_status'];to
//Set post status if ( wpuf_get_option( 'allow_status') == 'on' && isset($_POST['wpuf_post_status']) ) { $post_stat = $_POST['wpuf_post_status'];A few posts back me and loginid had the folowing conversation
Me
Edit Post doesn’t change the status of the post unless the post status field is allowed and the user changes it. However in the case the post status field is not enabled it would make sense to set the post status to the default if the current post status is draft.
loginid
Drawing on what you’ve said above, something you should consider also is that if a post is Approved / Published by an Admin. Then user goes back into dashboard, they can then edit that post and add whatever they wish and the post will still be in a Published state.
So for example a malicious user can add a good post, then once it has been Published, they can go back in and update with spam and the system will allow it and still see it as a Published post.This is a great suggestion and I have now added code to the next development release to do exactly what is suggested above.
ie If on editing a post the ‘Post Status’ field isn’t shown then on submit the post status should be reset to what is indicated by the Frontend option ‘Post Status’
loginid’s reporting of the following a few bugs back is indeed a bug
Also the child category for a post never seems to be picked up when editing a post from dashboard.
It only applies if the Frontend option ‘Category Selection type’ is set to ‘Ajaxified’. Basically what happens if a child category is selected then on the post being re-edited the child category is shown as ‘-Select-‘ instead of the child category itself being highlighted. Workaround till this is fixed is to use one of the other Category Selection types.
Hi Jonga.
WordPress 3.5.1 requires jQuery 1.8.3 and jQuery UI 1.9.2.
Strange that the members list author is loading those scripts from their own website rather than using WordPress’s version. As given (without seeing the rest of the script) this would cause problems with WordPress 3.4.2 and future WordPress versions. Also loading scripts twice as would happen with this code could cause problems.
The wp_enqueue_script excerpt you give is the way it should happen.
Try Firefox Firebug or Google Chrome – Developer Tools as shown on page 3 for user ‘loginid’ of my development thread to debug. The response to the admin-ajax.php ajax post on submit could be revealing
As for the jquery script my earlier suggestion of replacing jquery temporarily by a non-minimized version may not shown anything due to member’s list loading their own version. However it depends on which version of jQuery is in use at the time