professor99
Forum Replies Created
-
I have no idea. This is something Tareq (author of this plugin) and a few others have toyed with. Try searching this forum or the web for more info and if that fails add a forum post asking for more info. Maybe Aaron can help.
Hi SLogh,
Trying to figure this one out in order to provide a permament fix for the development version.
I’m kind of figuring out that later in the edit page loop it gets to the comment section which you guys have suppressed for the edit page (which makes sense). Now without the reset $post is not the original edit page page but the last post listed on the dashboard which in this case doesn’t have comments turned off.
Questions.
1. Given the above the comment would be for the last listed post. Not the edit page. Is this correct?
2. For testing purposes how did you suppress the comment field?
3. By line 272 I gather you really mean the next line?
4. This file has a have_posts() loop within another have_posts() loop though I’m not sure of the reason why. Why do you put the reset in the inner loop instead of after the outer loop?
5. Does putting wp_reset_postdata() just before the end of the function (line 304) work equally well?
Thanks
Problem is WordPress 3.5.
The latest development version fixes this
Unfortunately line2 in jquery.js.min is pretty much all of jquery. To find out exactly where you can install the non minimized version of JQuery which you can get from the JQuery website (check the WordPress version) and follow the stack trace in firebug. I generally rename the old version and use the same name for the un-minimised version (although there is an option somewhere you can set to use the unminified version).
MembersList is not listed as WordPress 3.5.1 compatible so I would check their forum. Most times these types of problems are caused by plugin/themes not using wp_enqueue_scripts to load scripts and an example of this I just solved is here where TheStyle theme caused problems with Frontend.
Hi JDking,
For the fork I don’t think you have to do anything in featured_image.js. It is really a submit check which is performed by the checkSubmit function in wpuf.js and the code needed is described in the previous article.
Other than that you just have to edit the function add_post_fields() in the file featured_image.php to add the classes “required” and “requiredField” much the same as described in the previous article.
The Post Expirator plugin is required for this. Other than that I know nuthing!
The development version does address this
Hi wpnovice,
For reference the edit links on my dashboard are of the http://%site%/%editPage%/?pid=136&_wpnonce=08420925a6.
Did you try using the 2010/2011 themes to see if any problems disappeared?
Also FrontEnd version 1.1 needs permalinks to have %postname% in them. The latest development version doesn’t require this.
Worth trying the development version anyway as it has lots of new features and bug fixes
For question 2 try the development version. Some performance issues were fixed there. Please report back if that does the trick
Hi Koruitch, development version 4.3 details can be found on page 2 http://wordpress.org/support/topic/frontend-updates-2rrr-fork/page/2?replies=73. Your bug above may be fixed by this version though it depends on how you call the page with the shortcode on it.
Hi koruitch,
Finding it a bit hard to understand you .
I think your referring to the normal TinyMCE “Visual/Text” tabs on the the text editor window which are missing in my screenshot.
The reason for this is I use a custom editor for this site.
If you want similar for your site the code for it is already included in the development version in the examples directory in the file Showtime example.php. Just include everything from the line below to the end of that file
//Add custom editor for WP User Frontend
I also talked about this on the forum
Thanks for your interest. I forgot about this when I took the screenshot so it could be a bit confusing.
We have discovered a bug with TheStyle theme from Elegant Themes with the development versions and WordPress 3.5.1.
With the above combination clicking on the attachment button (if enabled) will only result in FrontEnd scrolling to the top of the screen.
This problem exists because TheStyle theme presently uses a version of jQuery UI (1.7.2) which is incompatiable with WordPress 3.5.1 (which uses 1.9.2).
The fix is of to update TheStyle theme to use the jQuery version compatiable with the WordPress version it is installed on.
So in the directory /wp-content/themes/TheStyle do the following chages:
1. Add the following code to header.php just before wp_head()
<?php
//Used by /includes/scripts.php
wp_enqueue_script(‘jquery-ui-core’);
wp_enqueue_script(‘jquery-ui-effects’);
wp_enqueue_script(‘jquery-ui-widget’);
wp_enqueue_script(‘jquery-ui-tabs’);
?>2. Delete the following line from include/scripts.php
<script type=”text/javascript” src=”http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.1/jquery-ui.min.js”></script>
Hi djanael,
Have got some Portuguese translations that may help. If you send me your email I can link you up with the person who is doing the translation.
I could also post it here if you prefer.
My email abruinATihugDOTcomDOTau
Hi djanael,
I’m not familiar with translation tools. The WordPress article link is about as far as I go.
However it would be great is someone else could help.
Hi Djanael,
I’m not too sure how to do this myself but Frontends author Tareq has already installed a language pack for Bangla – Bengali.
Basically this is how I think it’s done. You need to create the following two files for your language pt_BR and install them in wp-user-frontend/languages.
wpuf-pt_BR.mo
wpuf-pt_BR.poThere are links for tools to do this in the following WordPress article on translations which gives a good explanation of the process.
I’ve already asked one of out Portuguese users to submit a translation but I know Brazilian is slightly different.
Also a translation for the development version would be fantastic