On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Unable to clone a WordPress instance that contains VIEW with a database user as DEFINER in its database: Access denied; you need (at least one of) the SUPER privilege(s) for this operation

Follow

Comments

8 comments

  • Avatar
    Olivier Charlier (Edited )

    Do you have an idea if it will be solved in the next release ? I'm using v4.8.3-3661 of WordPress ToolKit and I'm just a little confused of doing such changes manually to the DB, I prefer to use the "fixed version " of Wordpress Tool Kit.  Thanks in advance for your feedback

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Olivier Charlier

    This behavior is planned to be changed but later, For now, the planned version is 5.x.x. Priority may be changed depending on demand.

    0
    Comment actions Permalink
  • Avatar
    Rudolf Wagner

    Well the demand is definitely there. I wonder when the Wordpress toolkit is finally cloning without problems. It is probably one of the strongest selling points of Plesk for Wordpress hosting so it might be wise to change this priority and make it work flawless fast.

    2
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hello Rudolf Wagner we agree that there is demand and working on this issue. Currently, we plan it to fix in version 5.3 which is planned for Q1 2021

    0
    Comment actions Permalink
  • Avatar
    Brian Craigie

    I have the same error message but there are no results when I grep "view structure"...  However, there are many TRIGGER entries associated with CiviCRM: for example

    /*!50003 CREATE*/ /*!50017 DEFINER=`some_user`@`%`*/ /*!50003 TRIGGER civicrm_im_after_update after update ON civicrm_im FOR EACH ROW BEGIN

    Is this planned to be fixed too?  Is the solution the same, but to delete the TRIGGERs instead of the views?

    Thanks.

     

    0
    Comment actions Permalink
  • Avatar
    Davide Gennari (Edited )

    I've same error, never happened before, has anyone solved with suggested workaround?

    Can solution 1 proposed in this article https://support.plesk.com/hc/en-us/articles/360005033014 solve the problem momentarily?

    0
    Comment actions Permalink
  • Avatar
    Jean Hertz

    We moved on Plesk Obsidian and this article relates to Onyx.

    We thought this would finally work on Obsidian as promised but does not.
    When can we count on a wp cloning process that works?

    Thanks in advance.


    0
    Comment actions Permalink
  • Avatar
    Davide Gennari

    In my case I have temporarily solved by deleting a view from the database, it was a view of a plugin that required SUPER privilege(s) and that generated the error during cloning.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request