Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Sorry, the code should be changed to:
    if (wp_set_post_categories($id, $merged, false) == false) {

    Otherwise the email and/or debugging will not work correctly.

    I haven’t tested it, but it looks like this is possible in the plugin settings. Go to Settings -> Post Expirator and change the Default Date/Time Duration: from “None” to “Custom” and in the next field enter “+3 months”. That should set the default for any new pages / posts to +3 months from the Publish date.

    I had the same issue, but only if the original post had 1 category and I was removing that category. If the post had 2+ categories and I was removing 1 of them, then it worked. The way I fixed it was to edit post-expirator.php on line 758 and change:
    if (wp_update_post(array('ID' => $id, 'post_category' => $merged)) == 0) {
    to:
    if (wp_set_post_categories($id, $merged, false)) {

    Thread Starter sidtheduck

    (@sidtheduck)

    I know, it is weird!
    I don’t know what version of Linux its running. I could contact them to try to find out, but it was originally hosted by Speakeasy, which was bought out by Megapath, which is now owned by Global Capacity (client has been with them a long time) and Megapath doesn’t even show listings of webhosting options anymore (just cloud Exchange or Sharepoint options). None of the usual release/issue info in the /etc/ folder (for Debian-based or RHEL) and no lsb_release installed. uname outputs that it’s running on kernel 2.4.37.9 and the generic GNU/Linux category.

    I can try to dig more and see if there’s anything else I can find out. Thanks for checking back with me! I’ll let you know any info I come up with.
    Thanks.

    Sorry to hear that, mattcav. I don’t have access to a subdomain structure, but I’ll try to set up a test environment to do so. I’ll keep to posted to let you know if I find out anything.

    @mattcav,

    Didn’t realize you ran multisite! ??
    If you use site_url(), do you have access (or want access) to all images and galleries of all blogs associated with you multisite installation? If so, site_url() would be the way to go, but if not, network_home_url() might be the way to go. I’m not positive on the separation there as I do not have multisite to test in, but you may want to test both ways to see if it makes a difference and what you have access to. If it turns out that site_url is the way to go, we should try to report the tests to the NextGen bug report as it works either way on my system. Not sure how much has been done to make NextGen friendly with multisite.

    @corbanraun
    Glad it worked for you!

    I took a look through the changes that Alex Rabe did for the NextGen Gallery and he purposefully changed from site_url() to home_url() for this release. However, I did file a bug ticket to change from home_url() to home_url(‘index.php’) which specifies the actual WordPress file so that this should work correctly in all situations. He has made the changes to the code core and it should be in the next release.

    To test if this fix works for your system, change the code to:

    jQuery(document).ready(function(){
        jQuery("#gallerytag").nggAutocomplete( {
            type: 'gallery',domain: "<?php echo home_url('index.php'); ?>/"
        });
        jQuery("#albumtag").nggAutocomplete( {
            type: 'album',domain: "<?php echo home_url('index.php'); ?>/"
        });
        jQuery("#singlepictag").nggAutocomplete( {
            type: 'image',domain: "<?php echo home_url('index.php'); ?>/"
        });
    });

    if not, there may need to be some additional changes to the core (or to your site). My site works with the new code as well, so please test it out on your system.

    Thanks again to Alex Rabe for NextGen Gallery and for the quick response to bug tickets!

    I had this same error on one of the sites I run. Unfortunately, upgrading to WordPress 3.2.1 and updating to the current stable release of Next-Gen Gallery (1.8.2) did not fix it like Paul Chauvet.

    However, I was able to fix it. The issue came about that the site uses a different home page than the standard wordpress home page (to allow the blog and custom post types to have similar URLs).

    I was able to fix it by changing /wp-content/plugins/nextgen-gallery/admin/tinymce/window.php from this code:

    jQuery(document).ready(function(){
        jQuery("#gallerytag").nggAutocomplete( {
            type: 'gallery',domain: "<?php echo home_url(); ?>/"
        });
        jQuery("#albumtag").nggAutocomplete( {
            type: 'album',domain: "<?php echo home_url(); ?>/"
        });
        jQuery("#singlepictag").nggAutocomplete( {
            type: 'image',domain: "<?php echo home_url(); ?>/"
        });
    });

    to this code:

    jQuery(document).ready(function(){
        jQuery("#gallerytag").nggAutocomplete( {
            type: 'gallery',domain: "<?php echo site_url(); ?>/"
        });
        jQuery("#albumtag").nggAutocomplete( {
            type: 'album',domain: "<?php echo site_url(); ?>/"
        });
        jQuery("#singlepictag").nggAutocomplete( {
            type: 'image',domain: "<?php echo site_url(); ?>/"
        });
    });

    Correctly using the site_url() function of WordPress instead of the home_url() function

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