Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Author thaikolja

    (@thaikolja)

    Damn, that sucks. And thanks for bringing this to my attention. Do you have any more information on what might have been the cause?

    Plugin Author thaikolja

    (@thaikolja)

    Please enter the following into your wp-config.php and let me know the result:

    define("WP_DEBUG", true);
    define("WP_DEBUG_LOG", true);
    define("WP_DEBUG_DISPLAY", true);
    define("SCRIPT_DEBUG", true);
    
    @ini_set("display_errors", 1);  

    After that, please check your debug.log and let me know what it says.

    Thread Starter philsimon

    (@philsimon)

    Thanks.

    Here is the error log from my staging site.

    Plugin Author thaikolja

    (@thaikolja)

    Thanks for your quick reply, @philsimon. Please download the current development version, delete the official one from your web server, and replace it with this one. And then, please, let me know if that fixes the error so that I can push a hotfix.

    By the way: You can keep track of all pre-official changes here.

    Thread Starter philsimon

    (@philsimon)

    The dev plug-in doesn’t fix the issue unless there’s a caching issue. That’s doubtful, though, because there’s no caching on my staging site.

    Here is a pic showing live vs. staging. The latter’s got the dev version of the plug-in; the former’s showing v 2.0.4.

    Thanks.

    Plugin Author thaikolja

    (@thaikolja)

    That’s strange. Can you please clear your debug.log and give me the output – after experiencing the fatal error – again? That should make it clearer.

    Thanks for your patience!

    Edit: And please tell me what PHP version you use.

    • This reply was modified 3 years, 7 months ago by thaikolja.
    Thread Starter philsimon

    (@philsimon)

    Here are all log entries from today.

    Thread Starter philsimon

    (@philsimon)

    PHP: 7.4

    Thread Starter philsimon

    (@philsimon)

    <h3><span class="fun-hover2"><span style="color: #000000;"><?php echo get_secondary_title($post_id, $prefix, $suffix); ?></span></span></h3>

    I put this code in single.php so it displays underneath the title.

    Plugin Author thaikolja

    (@thaikolja)

    Thanks. Please try the latest development version.

    Plugin Author thaikolja

    (@thaikolja)

    From what I can see, the problem is that the variables in the parameters ($post_id, $prefix, …) have not been defined. In PHP, that means they have the type null. However, in the last version, I made things a bit stricter to only allow int and string types, respectively, to avoid unexpected outcomes. Always make sure to have variables defined; otherwise, try not to use them in parameters of functions. This will lead to errors like this ??

    Kindly let me know if the latest development version worked out for you. If not, please erase your debug.log and show me the newly generated one so I can inspect the bug.

    Thread Starter philsimon

    (@philsimon)

    Thanks. The dev version now works. I’ll keep the old one until 2.0.6 launches in the WP directory.

    Plugin Author thaikolja

    (@thaikolja)

    Thanks for your help! I’ll push the version in a few minutes. Please keep me informed if you encounter any bugs or errors. With 9000+ active installations and being the only developer, it’s pretty hard to avoid the occasional bug.

    I’m sorry for the inconvenience. If you like, I’d be happy if you left a review.

    Plugin Author thaikolja

    (@thaikolja)

    I’ve released the update. Please be so kind as to check if it all works as it should. And thousand thanks for your help!

    Thread Starter philsimon

    (@philsimon)

    ?

    I had left a review months ago.

    Thanks for the help!

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Latest Version Causes Posts to Crash’ is closed to new replies.