I can't figure out when and where it should be using

I can’t figure out when and where it should be using a specific single page template and the theme developer is pretty unresponsive :slight_frown: so is the plugin developer I’m using (http://wp-types.com/) I actually tried using custompress but these guys had more options when creating custom post types. For example, uploading a file. And they make it easy creating archive pages (as you can see from the example below)

When I try to click on of the projects below:

http://the3doodler.staging.wpengine.com/project/

And it comes to a blank screen:

http://the3doodler.staging.wpengine.com/project/zooey-warsi/

Ideas?

Thanks,

Faraz

  • Jack Kitterhing
    • Code Norris

    Hi there Faraz,

    I hope you are well today and thanks for your question.

    I checked out the links supplied, I’m not getting a blank page, I’ve got the Visa and other Payment provider logos along with the header and footer but no content in between that.

    So with this have you created a custom page template that you are using on that page? Would it be possible please to get a screenshot of how that page looks from the admin view in wp-admin > pages or your custom post type,

    That way I can see what content should be appearing and how you have it setup.

    Thank you!

    Kind Regards

    Jack.

  • Imperative Ideas
    • HummingBird

    I’m all ears. Have built pretty extensively with Types and am happy to help. Their paid support is actually quite good, if you don’t mind waiting a few hours for a reply.

    I can also tell you that your problem is that you are caching a site in development. Why on earth is there an advanced-cache.php error on a staging copy? Caching is for final deployment only man, it’s going to give you a million headaches in dev.

    Warning: include() [function.include]: Failed opening '/nas/wp/www/staging/the3doodler/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /nas/wp/www/staging/the3doodler/wp-settings.php on line 58

  • Imperative Ideas
    • HummingBird

    Well, that particular error occurs when WP SuperCache hasn’t been properly uninstalled/transferred. You can grab the file here:

    https://github.com/crowdfavorite-mirrors/wp-wp-super-cache/blob/master/advanced-cache.php

    and put it in /wp-content/

    That will get rid of the error but it won’t actually solve the problem of cleaning up the install. There will be entries in wp-config.php and htaccess at the very least.

  • Imperative Ideas
    • HummingBird

    Finally, if you aren’t adept at creating custom templates in PHP/HTML/CSS then think about ponying up the cash for wp-views.

    WP-Types, as a plugin, is super-powerful but it’s got a bitchin’ learning curve on all but the simplest things. That’s why it’s free… the back-end is like crack. You get a little and you want more but unless you are at an intermediate level with PHP (switch statements and array parsing are second nature to you), you’re going to need Views to pull it all together.

  • Faraz
    • Flash Drive

    I did buy wp-views. I configured wp-types perfectly. But the issue is that it;s not pulling the correct view. I set up three views for my archive pages:

    1. project-type (taxonomy): http://the3doodler.staging.wpengine.com/project-type/play/

    2. project tags (taxonomy): http://the3doodler.staging.wpengine.com/project-tag/yolo/

    3. all projects: http://the3doodler.staging.wpengine.com/project/

    As you can tell these work great. Customized them perfectly and easily. But when i created a view for the individual project page, all i see is a blank page. Here is an example of a single project:

    http://the3doodler.staging.wpengine.com/project/carly-rae-warsi/

    Does that make sense?

  • Imperative Ideas
    • HummingBird

    This is really a case where we need to look at the error log on that page, which also means eliminating as many PHP errors as possible before trying to dig into the specific cause.

    Go ahead and replace (in wp-content.php)

    // Enable WP_DEBUG mode
    define('WP_DEBUG', false);

    with:

    // Enable WP_DEBUG mode
    define('WP_DEBUG', true);

    // Enable Debug logging to the /wp-content/debug.log file
    define('WP_DEBUG_LOG', true);

    // Disable display of errors and warnings
    define('WP_DEBUG_DISPLAY', false);
    @ini_set('display_errors',0);

    This will have two immediate effects. The first is that you will no longer see PHP errors all over the place on your site. The second is that you will get a full log of errors in /wp-content/debug.log

    We'll want to look at the output of that file when attempting to load the single project page.

    In addition, we want to look into your JS Console errors. Let's see… the vast majority of these are being caused by a social media plugin that doesn't like the staging URL, so we can ignore them. The last one looks scary but it's a minor fix.

    Failed to load resource: the server responded with a status of 404 (Not Found) http://the3doodler.staging.wpengine.com/wp-includes/js/jquery/jquery-1.10.2.min.map
    GET http://the3doodler.staging.wpengine.com/wp-includes/js/jquery/jquery-1.10.2.min.map 404 (Not Found) /wp-includes/js/jquery/jquery-1.10.2.min.map:1

    That is actually a WP 3.6 error. You want to delete the whole second line starting with the @ in order to get rid of it.

    /*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license
    @ sourceMappingURL=jquery-1.10.2.min.map
    */

    So no, that's not the issue. Let's see the error log output.

  • Imperative Ideas
    • HummingBird

    Stick the log result at pastebin.com and put the share link here. Be sure to delete it when we are done so your full path isn’t hanging around on a shared resource.

    Also, clear your log file, hit refresh on the page one time, then read the log. If you go through 100 refreshes, that log could be 20,000 lines long if it’s a bad one.

  • Imperative Ideas
    • HummingBird

    The result should look like this:

    http://pastebin.com/eF2B9gSF

    That is an actual debug log on one of my dev sites (I don’t care about the path because it’s a localhost and not a public server)

    As you can see, I’ve got a “strict standards” warning due to the way a variable is passed by Advanced Custom Fields. It’s not actually an error, just a warning that its’ not the “right” way to do something. You’ll get a lot of these with WordPress, especially since the PHP version requirement just changed.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.