Missing *_timeranges tables, multi-site

  • dgorsline

    (@dgorsline)


    5 months, 2 weeks ago

    I manage a multi-site installation, all under [ redundant link deleted ]. I upgraded to Events Manager v7.2.3.1 on 19 December. Recently, I noticed the following problem behavior. When a new (non-recurring) event is created (via the UI) in one of my subsites (e.g., /johnclayton/), I see error.log messages like the following:

    2026.01.23. 12:34:08 [error] 61685#61685: *2283150 FastCGI sent in stderr: "PHP message: WordPress database error Table 'vnpsorg.wp_17_em_timeranges' doesn't exist for query …

    The event is successfully created, as far as I can tell. I don’t see any evidence of a problem in the UI.

    From the Network Admin console, I ran an Update Network (today) to make sure that my database is squared up with my software version.

    I have Enable global tables mode? set to Yes.

    I can reproduce the problem on both my live site and my staging site.

    I’d like to clear up the chaffy messages about the *_timeranges table. Any help is appreciated.

    —
    [ Signature, email and links deleted, please do not do that ]

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Support Moderator

    (@moderator)

    5 months, 1 week ago

    @dgorsline Please do not create multiple topics about the same thing phrased differently. I have archived your new topic.

    You can clarify in reply here.

    Thread Starter dgorsline

    (@dgorsline)

    5 months, 1 week ago

    I can clarify that the problem behavior is a likely software bug. I’ve examined my database schema. I have confirmed that, consistent with Enable global tables mode?=Yes, there are *no* tables named wp_<blog_id>_em_* for my 14 subsites; there are only tables named wp_em_*. (Exception: there is one subsite, ID 10, from an old setup that is no longer used.) And also consistent with Enable global tables mode?=Yes, all events are recorded in wp_em_events, with the appropriate ID set in the blog_id column.

    Any advice on this likely software defect is appreciated.

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

You must be logged in to reply to this topic.