Viewing 11 replies - 16 through 26 (of 26 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    Those are PHP Notices. They can’t be generated from PHP files if the PHP files aren’t actually there.

    For example, you have a message on the right there saying that the $post_type property is not defined on line 25 of the /var/www/htdocs/wp-admin/includes/meta-boxes.php file. That message cannot possibly be generated if the file doesn’t exist. Why line 25? Where did it get the $post_type variable from?

    The files do exist, or you’re not actually looking at the server you think you’re looking at, somehow.

    Thread Starter steelmaiden

    (@filipmedia)

    Ah yeah it is a docker setup, so i got confused. Those paths exist virtually, if you know what i mean. So this is not the problem after all, still lookint to find the real issue in that case ??

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    Any JavaScript errors in the console when you load that page?

    Thread Starter steelmaiden

    (@filipmedia)

    No errors, except that the favicon.ico is missing.

    Thread Starter steelmaiden

    (@filipmedia)

    Another error when i try to upload a media file to those broken sites:

    03988309.gif
    Could not insert post into the database

    Works just fine on sites where i can add new posts.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    Could not insert post into the database

    Hmm. That does suggest something is wrong with your tables, or they weren’t imported correctly, or something. Also given the thing you mentioned with wp_options earlier suggests that as well.

    That error very literally means that an SQL “INSERT INTO table” failed. So, yeah, check those main site tables. Maybe they’re really borked somehow. Run a repair on them. Compare them to the default schema. Something’s wrong there.

    Thread Starter steelmaiden

    (@filipmedia)

    Ok here is update with semi good news.

    I have re-imported the tables for my child sites and they work now.

    However, when trying to re-import my wp_options table via phpmyadmin for my main site i keep getting erros like this:

    **SQL query:**

    `

    — Indexes for dumped tables


    — Indexes for table wp_options

    ALTER TABLE wp_options
    ADD PRIMARY KEY (option_id),
    ADD UNIQUE KEY option_name (option_name)
    `

    **MySQL said:**

    #1062 - Duplicate entry '13770809' for key 'PRIMARY'

    I tried removing the rows with the 13770809 entry, but a new similar error comes up every time i reimport. How do i fix this, how do i force the table to import?

    • This reply was modified 5 years, 9 months ago by steelmaiden.
    Thread Starter steelmaiden

    (@filipmedia)

    I am not sure if this is the issue, but option_id in my wp_options tables start from number 3 and not number 1.

    Screenshot: https://community.easyengine.io/uploads/default/original/2X/9/97948fa96199ce5dad3408bd78c80776861ce757.jpeg

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    The option id is just a unique number, it doesn’t have to start at any particular point.

    However, having a duplicate option with ID 13770809 is a problem, so I’d say look at your data and see what that option actually is, and why you have two of them. Eliminate one of them.

    Thread Starter steelmaiden

    (@filipmedia)

    When i eliminate it, another one pops up… i already removed over 200 rows like this. Also they are not duplicates in the table i am trying to import, it just gives such an error for some reason.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    Maybe your export is bad. Look at it with a text editor. See if there’s some dupes there.

Viewing 11 replies - 16 through 26 (of 26 total)
  • The topic ‘WP editor problems for adding new posts after update’ is closed to new replies.