Errors using home_id in shortcode

Support has been upgraded!



The Support Forum is closed. Not to worry!  Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.

Premium Support

Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?

Please open a Support Ticket in your user account.

Click here to open a support ticket.

Free Support

Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.

Please open a new support topic in the WordPress support forums for Connections.

Click here to open a support topic.

This topic is: resolved

Tagged: 

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • 05/25/2018 at 8:08 am #463661
    Rich Anderson
    Participant

    I have two pages setup to display connections entries with enhanced categories. The first is the default Connections page and displays a category list and then just individuals.

    [connections list_type="individual" template="slim-plus" show_alphaindex='TRUE' show_alphahead='TRUE']

    Clicking on a category links takes you to the category with a list of associated individuals which is what we want. The search function and pagination buttons also behave as you would expect.

    The second page uses a custom template and the home_id attribute.

    [connections list_type="organization" template="slim-plus-courses" home_id="1932"]

    This page similarly shows a category list followed by the organization entries. Unfortunately when you click on a category on this page the site generates a 404 error. If I remove the home_id attribute, the link works, but it takes you to the default Connections page. The same behavior happens if you use the search field on this page.

    While they don’t generate 404 errors, when you click on the pagination buttons on this page, they just reload the current page so there’s no way to see information that isn’t on page 1.

    The difficult thing to track down here is what caused this, since all of this worked fine at the latest 9 months ago and the problem has just recently been brought to my attention. I haven’t made any changes to the custom template since it was working. I went into WordPress–>Settings–>Permalinks and saved the page to regenerate the permalinks, but that did not affect the behavior.

    Any ideas on what might be happening?

    05/25/2018 at 8:54 am #463666
    Steven Zahm
    Keymaster

    @ Rich

    If you are using a visual page builder either built in into the theme or added as a plugin and running Connections >= 8.19 , please try deleting and reinstalling Connections.

    Does that correct it?

    05/25/2018 at 4:48 pm #463682
    Rich Anderson
    Participant

    The site uses Page Builder and is currently running Connections 8.19.1. Removing the Connections plugin and reinstalling it did the trick with one caveat.

    I’m running Code Snippets to register some metabox fields in the Connections directory. When I tried to remove the Connections plugin, the WordPress admin white-screened on me. I had to change the folder name for Code Snippets to deactivate the plugin and regain access to the WordPress admin.

    Lesson learned…deactivate Code Snippets first.

    Thanks for the help and quick response!

    05/29/2018 at 12:43 pm #463927
    Steven Zahm
    Keymaster

    @ Rich

    What is the code in the snippet you’re running?

    05/29/2018 at 2:34 pm #463932
    Rich Anderson
    Participant

    There are several, but I’m guessing the one that caused the problem may have been the one that removes some metaboxes:

        add_action( 'admin_init', 'cn_remove_metaboxes' );

function cn_remove_metaboxes() {
    cnMetaboxAPI::remove( 'metabox-logo' );
    cnMetaboxAPI::remove( 'metabox-messenger' );
    cnMetaboxAPI::remove( 'metabox-social-media' );
    cnMetaboxAPI::remove( 'metabox-links' );
    cnMetaboxAPI::remove( 'metabox-date' );
}

    I’m not a coder, but it seems like there should be a test to see if something is there before it attempts removing it?

    I’ve also attached a file with all the snippets I’m using.

    Attachments:
    You must be logged in to view attached files.
    05/29/2018 at 2:53 pm #463934
    Steven Zahm
    Keymaster

    @ Rich

    Something like this would be safer:

    add_action( 'admin_init', 'cn_remove_metaboxes' );

function cn_remove_metaboxes() {

    if ( class_exists( 'cnMetaboxAPI' ) ) {
        cnMetaboxAPI::remove( 'metabox-logo' );
        cnMetaboxAPI::remove( 'metabox-messenger' );
        cnMetaboxAPI::remove( 'metabox-social-media' );
        cnMetaboxAPI::remove( 'metabox-links' );
        cnMetaboxAPI::remove( 'metabox-date' );
    }
}
    05/29/2018 at 3:15 pm #463937
    Rich Anderson
    Participant

    Makes sense. Thanks for the improvement.

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)

You cannot reply to this support topic. Please open your own support topic.