Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • migf1

    (@migf1)

    I just d/led the plugin and noticed the same problem (I’m on wp 3.7.1).

    Replacing the depreciated function split(...) with the function explode(...) in the files: wp-native-dashboard.php and automattic.php inside the plugin’s folder seems to fix the problem.

    It should also run a bit faster since explode() does not use regular expressions (neither does the plugin for those particular tasks, so split() was an overkill anyway, or so I think).

    Hope it helps. Btw, kudos to the author of the plugin, it seems really-really useful.

    @larry, from what I can tell you haven’t disabled the sidebar from your full-width template file. Try removing (or commenting out) the line:

    <?php get_sidebar(); ?>

    from your custom template file.

    @zulfikar: Thanks for the original post, which gave me a head start. However, the proposed solution does not retain the original font style of the page title, neither its vertical margin.

    For me, the following approach seems to work better for a full width page template…

    in child-theme’s style.css:

    ...
    .my-full-size {
    	margin-left: auto !important;
    	margin-right: auto !important;
    	height: auto;
    	padding-right: 1em !important;
    }

    And then, in my full-width-page.php file I just add the my-full-size class to the desired elements:

    ...
    <?php /* The loop */ ?>
    <?php while ( have_posts() ) : the_post(); ?>
    
    	<article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
    		<header class="entry-header my-full-size">
    			<?php if ( has_post_thumbnail() && ! post_password_required() ) : ?>
    			<div class="entry-thumbnail">
    				<?php the_post_thumbnail(); ?>
    			</div>
    			<?php endif; ?>
    
    			<h1 class="entry-title my-full-size"><?php the_title(); ?></h1>
    		</header><!-- .entry-header -->
    
    		<div class="entry-content my-full-size">
    			<?php the_content(); ?>
    			<?php wp_link_pages( array( 'before' => '<div class="page-links"><span class="page-links-title">' . __( 'Pages:', 'twentythirteen' ) . '</span>', 'after' => '</div>', 'link_before' => '<span>', 'link_after' => '</span>' ) ); ?>
    		</div><!-- .entry-content -->
    
    		<footer class="entry-meta">
    			<?php edit_post_link( __( 'Edit', 'twentythirteen' ), '<span class="edit-link">', '</span>' ); ?>
    		</footer><!-- .entry-meta -->
    	</article><!-- #post -->
    
    	<?php comments_template(); ?>
    <?php endwhile; ?>
    ...

    This also seems to behave closer to the original behavior of the theme, which centers the <article> elements, leaving plenty of room at both sides (although it leaves more room than the above css).

    I haven’t tested it extensively, but so far it seems to work fine.

    Thread Starter migf1

    (@migf1)

    Thank you for the rapid response! I’m marking the thread as resolved, although I’ll apply your suggestion later in the day (if anything else come up I’ll open a new thread).

    Thanks again!

    I’m not sure but I think this behavior is due to the existence of too many files present in your wp installation directory.

    You may try the plugin in a fresh WP installation, or by removing themes and plugins you do not use.

    Alternatively, you may try fiddling with the Explorer Scanner settings. They are explained in the docs but I haven’t really taken the time to read them comprehensively (I think one of the reasons could also be due to limited PHP memory, so you may have to increase it).

    Thread Starter migf1

    (@migf1)

    Ok, the problem was that I had a couple of video titles containing double-quotes, and apparently the plugin didn’t like that ??

    I fixed those titles and it now works fine!

    Hi Byron,

    first of all I’d like to thank you very much for your excellent photosmash! I’m using it extensively on my community site for more than a year and I’m pretty sad hearing you’re shutting it down.

    I’m also using NextGen on the same time, for different purposes (ngg for slideshows, ps for user uploads and star ratings, to name just a couple of examples).

    I really hope you reconsider, it will be such a pity for one of the most robust, well designed, functional and excellent supported plugins of WordPress to vanish just like that.

    There will always be poor ratings, no matter what (even wordpress itself gets lots of poor ratings form time to time :p)

    There are always ways to keep things under control, John25 already mentioned one. On the other hand, if your decision is indeed final, we ought to respect it, to thank you for your hard work all this time and to wish you all our best for your future activities.

    Best regards!

    Thread Starter migf1

    (@migf1)

    Hello, thank you for keep looking into it! I just tried with the default plugin settings but it was not working right. It could be that I have also tweaked ng-gallery’s css (dunno).

    Since I managed to screw up everything (lol) I have temporarily deleted ngg-voting. I will install it again when I have more free time to fiddle with it again, and I’ll let you know.

    If you find anything in the meanwhile, I’d be happy to hear about it ??

    Best regards.

    Thread Starter migf1

    (@migf1)

    Good morning, thank you very much for your efforts to improve this very useful plugin! It now works with [nggtags], however it seems to still have some issues.

    I’m using my own set of icons for the stars, which visually get corrupted on mouseover when in [nggtags] output screens (I haven’t tried with the default stars yet, but in [nggallery] output screens they work nicely).

    The most important issue though is that when one rates any image in [nggtags] genertated screens, the registered vote is always one star short (i.e. if you rate an image with say 4 stars, it registers the vote as 3 stars, and so on.)

    You can see an example of the above in the following links (they are form my site). The first one is a normal [nggallery] output screen, while the 2nd one it is generated via the [nggtags] shortcode:

    1. [nggallery] output
    2. [nggtags] output

    I’m really excited about this plugin and I’m really happy you keep supporting it!

    Best regards.

    Thread Starter migf1

    (@migf1)

    Thank you very much, I really hope you can fix it ??

    Best regards!

    Hello, thanks for this very nice and useful plugin!

    I’m particularly interested on the image voting thingy, which works as expected as long as I display the images via the [nggallery] shortcode.

    However it is not working when displaying images via the [ngtags] shortcode. It displays the rating stars but when you try to vote, it shows the loading gif and after a short while it displays the following error-message: “There was a problem saving your vote, please try again in a few moments“.

    I hope there’s a fix for this, because I have built up my whole gallery system on image tags.

    Thanks in advance!

    migf1

    (@migf1)

    I was wondering the same.

    I’m having exactly the same problem with version 0.31 which I just installed (I just discovered Mingle).

    Now, it doesn’t even let users delete their avatars and they are stuck with this error shown on the top of the screen.

    Moreover, it shows the same error whenever they try to login (those who have tried to change their avatars).

    Thanks for any solution you may give!

    On top of what the other guys said, I’d like to add that Sayotan also provides superb support on the theme’s forum!

    As far as i am concerned, Sayotan you deserve a big thank you and a great deal of respect!

    Thread Starter migf1

    (@migf1)

    Problems solved!

    First I followed this suggestion and my thumbnails aligned correctly again (many thanks), and then I updated the Settings->Miscellaneous Settings->Store uploads in this folder to the migrated relative path… after that I was able to specify the imagerotator.swf path in the Gallery Options->Slideshow screen.

Viewing 15 replies - 1 through 15 (of 15 total)