englebip
Forum Replies Created
-
Forum: Plugins
In reply to: [qTranslate] qTranslate not yet ready for the new version of WPYou could also manually change the affected qTranslate file, as described here: http://www.qianqin.de/qtranslate/forum/viewtopic.php?f=3&t=3240#p10666 .
As zhenya said, the development version (v 2.5.29b) already takes care of this: http://plugins.trac.wordpress.org/changeset?reponame=&new=534439%40qtranslate&old=500157%40qtranslate
Also, I just noticed that the
all-fieldsplugin overrides the hidden field plugin, so that it is no longer possible to select ahiddenfield from the dropdown list when adding a new field.Using WP 3.3.1 here.
You would need to use some JavaScript to show/hide certain fields based on a condition. See, for example, this post. You can include the code between
<script></script>tags above the code for the form.Forum: Plugins
In reply to: [Yoast Duplicate Post] [Plugin: Duplicate Post] Errors in Version 2.0I found a bug in version 2.0; at least when duplicating a custom post there are multiple notices and errors. They go away by modifying around line 271 of
duplicate-post-admin.phpby the following code:if ($post->post_type == 'page' || (function_exists('is_post_type_hierarchical') && is_post_type_hierarchical( $post->post_type ))) do_action( 'dp_duplicate_page', $new_post_id, $post ); else do_action( 'dp_duplicate_post', $new_post_id, $post ); return $new_post_id;The changes are in quoting
is_post_type_hierarchicaland changing$new_idby$new_post_idin thedo_action()calls.Forum: Plugins
In reply to: NextGen Gallery Themes\Templates?Can you say exactly what you’re doing? How did you set up your galleries and what code you’re using?
I think that it has to do with one of your plugins interfering with the display. Try disabling the Fancybox for WordPress plugin and see if that solves it. You can change how the large pictures are displayed under Gallery > Options > Effects.
Thanks freckleboy; my settings actually have
PHP Memory Limit : 128, so that may be indeed the issue.Hi Mark, your report does not provide enough info to troubleshoot… Did you check looking at the source code of the page (Ctrl+U/CMD+U on Firefox)? That might tell you something else about what is being loaded.
You can input a gallery by entering
[ slideshow id=x ]in a post or page; this way you can customize each gallery. You can see more examples here Does this help?If you go to Gallery > Overview > Plugin check (click on the button) and Server settings, do you see anything out of the ordinary? Is the GD library installed?
Forum: Fixing WordPress
In reply to: NextGen Gallery triggers 404 and MySQL errorWhich version of WP and NGG are you using? I’m looking at the code of
manage.phparound line 570 but I can’t find anything that would cause aDivision by zeroerror…There are 2 levels to organize pictures in NGG: galleries and albums. Albums can contain galleries, and also other albums (i.e., albums can be nested).
According to what you say, each of your “zip” files would go to a gallery, and you can then arrange the grouped ones in an album (e.g., one per event). Then you have the choice to display the album (with the 5 galleries) or each gallery individually.
You can start creating some galleries and then go to Gallery>Album to organize the albums with the drag-and-drop interface.
As far as I understand, you need to specify an
id=xparameter when calling[slideshow], with x being the gallery_id of the gallery you want to base the slideshow in. So unless you have all your pictures in a single gallery, it is not possible out f the box.One solution would be to create an album that contains all the galleries, and then create the slideshow based on this album. Not sure if that will work, though…
On the left sidebar on the admin interface, you can go to Gallery>Manage Gallery, then select the gallery you want to edit. You can add a Title and a Description to each picture; how they are displayed depends on how you are displaying the picture and can be customized.
Forum: Plugins
In reply to: Nextgen Gallery Plug in – Problem loadingI was having the same issue at some point, but after a few updates it is now solved. Are you using the latest versions, i.e. WP 3.2.1 and NGG 1.8.2? If not, upgrade and try again.