• Resolved regisit

    (@regisit)


    Working great when viewing a particular product category (e.g. /product-category/cabinets), but when viewing the entire shop (/shop/) it’s breaking the site and giving a blank page.

    Deactivate the plugin and /shop/ works fine; reactivate and blank page. Not getting any kind of PHP error – just an empty page. And I mean empty – nothing at all returned i.e. no HTML!

    https://www.ads-software.com/plugins/woocommerce-products-per-page/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Jeroen Sormani

    (@sormano)

    Hi,

    Thanks for the message.

    The white page means that there is a error, its just not shown. Could you turn on WP_DEBUG and let me know what message there is shown?

    From there I should be able to see whats up and what possibly could be done to get it compatible

    Thanks!
    Jeroen Sormani

    PS. please do note that I try my best, but support on specific themes is limited.

    Plugin Author Jeroen Sormani

    (@sormano)

    Hi,

    Thanks for the message.

    The white page means that there is a error, its just not shown. Could you turn on WP_DEBUG and let me know what message there is shown?

    From there I should be able to see whats up and what possibly could be done to get it compatible

    Thanks!
    Jeroen Sormani

    PS. please do note that I try my best, but support on specific themes is limited.

    Thread Starter regisit

    (@regisit)

    Hi Jeroen,

    I enabled debug when I noticed this issue. All that’s logged is some notices about theme/plugins that are still using deprecated functions or haven’t been updated for WP changes. These are logged whether your plugin is enabled or not. So no clue there I’m afraid! Also enabled PHP error logging – nothing there either.

    [29-Jul-2015 08:32:38 UTC] PHP Notice:  get_settings is <strong>deprecated</strong> since version 2.1! Use get_option() instead. in /home/rit0043web/public_html/wp-includes/functions.php on line 3391
    [29-Jul-2015 08:32:38 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /home/rit0043web/public_html/wp-includes/functions.php on line 3560
    [29-Jul-2015 08:33:02 UTC] PHP Notice:  get_settings is <strong>deprecated</strong> since version 2.1! Use get_option() instead. in /home/rit0043web/public_html/wp-includes/functions.php on line 3391
    [29-Jul-2015 08:33:02 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /home/rit0043web/public_html/wp-includes/functions.php on line 3560
    [29-Jul-2015 08:33:04 UTC] PHP Notice:  get_settings is <strong>deprecated</strong> since version 2.1! Use get_option() instead. in /home/rit0043web/public_html/wp-includes/functions.php on line 3391
    [29-Jul-2015 08:33:11 UTC] PHP Notice:  get_settings is <strong>deprecated</strong> since version 2.1! Use get_option() instead. in /home/rit0043web/public_html/wp-includes/functions.php on line 3391
    [29-Jul-2015 08:33:11 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /home/rit0043web/public_html/wp-includes/functions.php on line 3560

    Tks, Adam

    Plugin Author Jeroen Sormani

    (@sormano)

    Hi Adam,

    Did you check the page that turned white before when you enabled the plugin?
    On that page you should see the error when WP_DEBUG is on (maybe you do need to turn the ‘error logging’ off to make sure its outputted on the white page.

    Thanks,
    Jeroen

    Thread Starter regisit

    (@regisit)

    Hi Joren,

    Before plugin was installed all working fine including main /shop/ page. I added the plugin and category pages are fine but not front /shop/ page. De-activate plugin and /shop/ works again. Activate and it stops.

    Same errors as above were reported on the “white” page with just define(‘WP_DEBUG’, true) set (so it displayed errors on the front end). That is, I got the WP notifies but nothing else.

    I’ve since left debug on but set to log to file only. I can’t leave errors displaying on the front end – site is now live, but log file should have everything WP is reporting.

    It’s a mighty strange one – no page but no Apache, PHP or WP errors either!

    Tks, Adam

    Thread Starter regisit

    (@regisit)

    Hi Joren,

    Problem resolved! WP needed more memory!! Spotted by YiThemes support investigating why sitemap page wouldn’t build. After increasing memory [wp-config.php – define(‘WP_MEMORY_LIMIT’, ‘256M’)] I thought I’d try enabling your plugin again – and this time it worked on the main /shop/ page.

    Did decide against having an “all” option though – 600+ products listed at once is not good!!

    Thanks for your support,
    Adam

    Plugin Author Jeroen Sormani

    (@sormano)

    Hi Adam,

    Ahh, glad thats resolved now!

    Loading 600 products can be harsh on a server ??

    Thanks for letting me know!

    Cheers,
    Jeroen Sormani

    Thread Starter regisit

    (@regisit)

    NP – and sorry for calling you Joren! Need my glasses!!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Not working correctly with YiThemes’ is closed to new replies.