db only – no posts blank database

  • Resolved acteventsplanner

    (@acteventsplanner)


    8 years, 4 months ago

    Been using duplicator for a 2 years, never seen anything like this. From our server I created a database package only. On the live www site, ran installer as normal, but when I login, there is no data
    myphpadmin also reveals no posts..
    no errors..

    Please help our website is down

    tried to manually upload the sql in myphpadmin to get this error
    SQL query:

    # Table structure of table KACBYvNuposts

    CREATE TABLE KACBYvNuposts (
    ID bigint(20) unsigned NOT NULL AUTO_INCREMENT,
    post_author bigint(20) unsigned NOT NULL DEFAULT ‘0’,
    post_date datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
    post_date_gmt datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
    post_content longtext COLLATE utf8mb4_unicode_ci NOT NULL,
    post_title text COLLATE utf8mb4_unicode_ci NOT NULL,
    post_excerpt text COLLATE utf8mb4_unicode_ci NOT NULL,
    post_status varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ‘publish’,
    comment_status varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ‘open’,
    ping_status varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ‘open’,
    post_password varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
    post_name varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
    to_ping text COLLATE utf8mb4_unicode_ci NOT NULL,
    pinged text COLLATE utf8mb4_unicode_ci NOT NUL[…]
    MySQL said: Documentation

    #1214 – The used table type doesn’t support FULLTEXT indexes

Viewing 7 replies - 1 through 7 (of 7 total)
  • Cory Lamle

    (@corylamleorg)

    8 years, 4 months ago

    Hey @acteventsplanner,

    Thanks for the feedback! There are a few items in the FAQ that may provide a solution to this issue, this one may get you going.

        – What is Compatibility mode & ‘Unknown collation’ errors?
        – https://snapcreek.com/duplicator/docs/faqs-tech/#faq-installer-110-q

    Seems like you may need to update the MySQL server to match the same version where it was built, otherwise, you might try the different database build modes PHP/mysqldump

    Let me know if any of them help~

    Thread Starter acteventsplanner

    (@acteventsplanner)

    8 years, 4 months ago

    Hi Cory thanks for the response, We had this issue before then you added the feature, apply legacy.. which I always do in this case, because our staging server is offline
    our live server is through a host, and we have no control of updating MySql Server.

    I guess since legacy no longer works, then i must do the last option, and I don’t know were to find that option.

    My colleague thought it was due to this error
    #1214 – The used table type doesn’t support FULLTEXT indexes

    I will try a test on our staging again, or create a live test database
    and let you know the results.

    Cory Lamle

    (@corylamleorg)

    8 years, 4 months ago

    I believe FULLTEXT indexes are supported in InnoDB tables only starting from MYSQL 5.6 so you may have to change your table type if you can’t update MYSQL or alter table’s engine.

    Most good hosts will have an upgrade path for you to take, which would be the easiest.

    Thread Starter acteventsplanner

    (@acteventsplanner)

    8 years, 4 months ago

    Cory
    Thanks for your quick reply. Ok that error was to the manual myphpadmin import.
    Can I send you the install log using duplicator installer ?
    I don’t want it here because it is public. My email is [email protected]

    Cory Lamle

    (@corylamleorg)

    8 years, 4 months ago

    Hey @acteventsplanner,

    There really isn’t too much Duplicator can do to solve the issue, it has to be solved at the database level however, I can still look at your ticket if you want. If you want to submit a support ticket for this issue I can have a closer look at the log. Please provide a link to this thread when submitting the ticket.

    Thanks~

    Thread Starter acteventsplanner

    (@acteventsplanner)

    8 years, 4 months ago

    I used Use Database Full Search Mode from the www to our internal server it worked..
    i will have to try reverse back.. i think that is the key because there are some things normal search and the Unyson plugin the theme is built on, does not jive together for example.
    attachments which the problem here.. show this
    :{“attachment_id”:”2407″,”url”:”\/\/gayweddingsspain.com\/gaytesting\/wp-content\/uploads\/2018\/01\/gay-marriage-wedding-vows-100815-02-1.jpg”},
    so your normal search and replace does get the \/\/ i think..
    this is the problem i contacted the plugin author about this.. but now with database full search it worked

    Cory Lamle

    (@corylamleorg)

    8 years, 4 months ago

    That is good to know, thanks for the update!

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

The topic ‘db only – no posts blank database’ is closed to new replies.