• Resolved tommcgee

    (@tommcgee)


    My server log shows:
    2026/06/22 10:25:17 [error] 75915#75915: *2221245 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /www/blogsshuedu_468/public/wp-content/plugins/cool-timeline/includes/shortcodes/class-ctl-loop-helpers.php:216

    This is line 216:
    $ctl_story_date = $ctl_story_type[‘ctl_story_date’];

    Maybe it’s trying to access a string offset of something that’s not an array?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author CoolHappy

    (@narinder-singh)

    Hi @tommcgee,

    Thank you for reporting this issue.

    Based on the error message, it appears that the variable $ctl_story_type is expected to be an array, but it is receiving a string instead. We need to investigate further to determine why the value is not in the expected format.

    Could you please share the URL of the page where you have added the timeline?
    Also, let us know if the issue occurs on all timelines or only a specific one.

    This information will help us reproduce the issue and identify the root cause.

    Thread Starter tommcgee

    (@tommcgee)

    I only have one timeline running, and it’s on this page:
    https://blogs.shu.edu/baoxuemi/the-chinese-in-america/

    I applied a one-line patch, which is why it’s working now.
    $ctl_story_date = is_array( $ctl_story_type ) ? $ctl_story_type['ctl_story_date'] : get_post_meta( $post_id, 'ctl_story_date', true );

    Plugin Author CoolHappy

    (@narinder-singh)

    Glad to hear that the quick patch has resolved the issue on your site.

    Our team will investigate the root cause in more detail to understand why $ctl_story_type is not always returned in the expected format. Based on our findings, we’ll work on implementing a proper fix in an upcoming plugin update.

    Thank you for reporting this issue and sharing your workaround.


    Plugin Support Aniket Dogra

    (@aniketji)

    Hi @tommcgee,

    Thank you for your patience.
    We’ve fixed this issue and included the fix in the latest plugin version 3.3.4. Could you please update the plugin and verify it on your end?
    If you encounter any issues or have any questions, please feel free to reach out. We’ll be happy to assist you.

    Thanks & Regards

    Thread Starter tommcgee

    (@tommcgee)

    Looks like it’s working now, thanks!

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.