Forum Replies Created

Viewing 15 replies - 61 through 75 (of 199 total)
  • Interestingly i am looking into this too. I notice prettyPhoto script (assuming you are using that within this plugin) has a tutorial on how to do this and so i will read up and see. This plugin is only a wrapper so the tutorial should work: http://www.no-margin-for-errors.com/blog/2010/09/28/tutorial-opening-custom-content-in-prettyphoto/

    ^^–oops forgot to mention..if you go with the 3rd option (my sample code) you simply add this into your functions.php file (found in your theme’s folder). Sorry, just noticed i forgot to mention that (and this site doesnt allow me to edit what i wrote).

    The problem is because this plugin is putting in a “-” even for non-galleries for the data-rel attribute. Doing so confuses prettyPhoto.js file into thinking both are galleries and hence enables nav bars even for 1 photo.

    The fix is easy. One can either change the jquery.prettyphoto.js file (line 149) from:

    galleryRegExp = /\-(?:.*)/;
    to
    galleryRegExp = /\gallery(?:.*)/;

    Or this plugin can simply just stop using “-” for single images (non-galleries). It’s used for non-galleries to # each image in a post e.g. lightbox-1, lightbox-2,….lightbox-n, where n is the total # of images in a post. Not sure why this is necessary unless the author is making it universal so it works across the other scripts (essentially you only need to have a data-rel=”lightbox” not data-rel=”lightbox-1″..) So if u have 1 image it is called: lightbox-1. Because of this “-” prettyPhoto then thinks it is a gallery and hence shows the nav bar.

    Alternatively, if you dont want to touch the author’s plugin php file nor the prettyPhoto.js file you can add a wordpress filter that looks for “lightbox-[0-9]+” and replace it with “lightbox”, stripping the “-” from the content before it is sent out to the browser. At least that way if this plugin updates your changes will still work. For example (this should work and still allow galleries to work too):

    function my_the_content_filter($content)
    {
         $content = preg_replace('/lightbox-[0-9]+/i','lightbox',$content);
         return $content;
    }
    add_filter( 'the_content', 'my_the_content_filter',99 );

    Cheers
    Kimberly

    I might be wrong but i notice the nav bar/next/prev buttons are the result of the prettyPhoto.js file which this plugin is more a wrapper around some other person’s work. Not sure if this javascript file was updated and doesnt check for your condition (1 image per post). I checked the js file and it looks relatively easy to fix the problem.

    Hi again! I checked your site and my first thought was the same as @dfactory that you are linking to a very old jQuery verion (latest is 1.11.x = 2015, yours is 1.7.2 = 2012) but upon further inspection i do find it interesting that your posts work fine with the same older jquery and so jquery is not the issue. I did a firebug inspection and see no errors on your page so RL isnt experiencing any problems there.

    Btw, since you are indeed using the latest WP and it already comes with the latest jquery its possible you have a plugin that is overriding and including this older jquery (maybe u did this a long time ago and forgot about this plugin?) or you have:

    wp_deregister_script('jquery');
    wp_enqueue_script('jquery', "https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js",array(),null);

    in your functions.php. Check for it in that php file and remove them. This will allow WP to include the newer jquery.

    Anyway, back to your problem. I am going to do some more hunting around and will get back to you.

    Btw, I do find it interesting that when i modify your post’s data-rel attribute from lightbox-0 to lightbox the image RL pop up finally works properly.

    Try replacing rel="lightbox" with data-rel="lightbox"

    That’s why i never update for a few versions when out of the blue authors eagerly post a new version proclaiming: “rebuilt from scratch”. Inevitable bugs abound.

    Not sure if u are afraid to get your hands dirty but its fairly easy if you are willing to open a php file. Let me know and i will tell you.

    if it helps the easiest way would be to simply add an entry into your htaccess file that does what you want.

    I have never played with Covert VideoPress but it sounds to me from what u are saying that it is not generating the standard xml sitemap format that Google needs and as such my guess is having XML Sitemap Generator enabled would be fine.

    Can you enable this plugin and peruse the page to ensure all your video pages are included? If so then you may just only need to disable thei video sitemap generator.

    Did you resolve the problem?

    If u make use of a page/post cache system like Quick Cache you can have this plugin monitor the cache files..any changes that appear will let you know (assuming you turn off date changes). Some times these cache type plugins may add a footer indicating the cahce was updated..that would need to be turned off or u will get false positives.

    Besides that you would need to write a plugin that could routinely check your posts in the dbase. It’s quite simple to do — even now i have thought up the code in my head.

    1. It runs at the intervals when they are set (so if u set it at 3:00pm your time then hourly will run at precisely 4:00pm and so on).

    2. You can use any email here (existing or not existing) — it doesnt care.

    3. Use wildcard “*” otherwise it is looking for a precise match. You can use “*” at the beginning and end e.g. *wp.jpg*

    Check out some of my replies to people in this support forum. It will save me time having to repeat myself again (done it so many times already).

    If you’re getting locked out you can jump into mySql and delete the ban entry found under your wp_post table. It will have your ip address there. You can then check out the intrusion table for your ip and see which entries were blocked. Use those to set an exception.

    Sorry for not giving more details but my guess is you’ve probably moved on.

    Kimberly

    (@kellogg9)

    That’s very strange never seen this plugin do that.

    Your case however might be a really simple solution and might only require you to hunt through its Options to disable the prefix. Its been a long time since i looked at this plugin so i cant say.

    I actually made my own forked version of this plugin but because i havent looked at the code in a year or so i am hesitant to share it despite ti working flawlessly still without any need for me to dust off my coding skill. This place was very active some time back with a bunch of us fixing a bunch of its problems and forking but it seems we all got carried away that we forgot to release it to others. However, i just noticed now that one of us apparently did release their forked version: http://wordpress.org/plugins/wp-minify-fix/

    So you can try that one out and see if it works. If it doesnt then i might consider sending you my version since it does have a lot of fixes and a bit more streamlined/efficient than what the author intended.

Viewing 15 replies - 61 through 75 (of 199 total)