Support

Account

Home Forums General Issues Cloning a site with Custom Fields to a subdomain

Solved

Cloning a site with Custom Fields to a subdomain

  • In short, due to conflicts with the blog, I duplicated a site and database with Advanced Custom Fields from:
    http://goldhillmuseum.org.uk/
    to
    http://shaftesbury-remembers.goldhillmuseum.org.uk/
    I did a search and replace for the domain on the db and removed the old site content. All works fine except you get a blank page when you click on the new custom post types (“stories”). Go here to see what I mean:
    http://shaftesbury-remembers.goldhillmuseum.org.uk/stories/
    This is the old site where the stories work okay:
    http://goldhillmuseum.org.uk/great-war/stories/
    I am obviously missing something. Can anyone help?
    Thanks
    Rob

  • Hi @fanlokbun

    Could you please set WP_DEBUG to true to see any error messages on the page? Please take a look at this page to learn how to set it: https://codex.wordpress.org/Debugging_in_WordPress.

    I’ve also checked your page but it looks great for me. Did I miss something?

    Thanks πŸ™‚

  • Hi James,

    I have set WP_DEBUG to true. The error I get when I click on an individual story is below*. I have checked the working site and the error seems to be the same except different urls. I don’t really understand what they mean so any help or advice would be most appreciated.

    This is the site giving errors:
    http://shaftesbury-remembers.goldhillmuseum.org.uk/stories/
    If all looked okay to you I am guessing you were looking at the origin site that is still working fine.

    Many thanks for your help

    Rob

    *Error:
    Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /customers/0/4/2/goldhillmuseum.org.uk/httpd.www/shaftesbury-remembers/wp-includes/functions.php on line 3897 Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /customers/0/4/2/goldhillmuseum.org.uk/httpd.www/shaftesbury-remembers/wp-includes/functions.php on line 3897 Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /customers/0/4/2/goldhillmuseum.org.uk/httpd.www/shaftesbury-remembers/wp-includes/functions.php:3897) in /customers/0/4/2/goldhillmuseum.org.uk/httpd.www/shaftesbury-remembers/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries.php on line 32 Parse error: syntax error, unexpected ‘{‘, expecting ‘(‘ in /customers/0/4/2/goldhillmuseum.org.uk/httpd.www/shaftesbury-remembers/wp-content/themes/enfold/single-story.php on line 4

  • Hi @fanlokbun ,

    Thanks a lot for sharing with us.

    From your error log it seems you have some syntax error in your template file single-story.php

    Kindly check on line 4 as indicated.

    unexpected β€˜{β€˜, expecting β€˜(β€˜ in /customers/0/4/2/goldhillmuseum.org.uk/httpd.www/shaftesbury-remembers/wp-content/themes/enfold/single-story.php on line 4

    Let me know how it goes.

  • Thanks James,
    I copied single-story to my child theme and replaced the { with a ( like suggested. Now it starts to load and I get the following error:

    Contributor: Fatal error: Call to undefined function types_render_field() in /customers/0/4/2/goldhillmuseum.org.uk/httpd.www/shaftesbury-remembers/wp-content/themes/enfold-child/single-story.php on line 8

    Any ideas what is going on?
    Much appreciated.
    Rob

  • Hi @fanlokbun

    It seems the issue is related to Toolset Types Fields. It’s possible that the plugin is not loaded yet. If you use Toolset Types Fields, could you please getting in touch with their support instead?

    Thanks πŸ™‚

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.