Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter gordboy

    (@gordboy)

    Further info, in 1.4.2 clicking the “SQL command” link shows

    DROP TABLE ;

    in other words the selected table names are not being passed to the function “drop_tables” in mysql.inc.php, in the $tables var presumably.

    For 1.3.2 the “SQL command” link shows

    DROP TABLE ‘fred’ ;

    as it should.

    Let me make one thing absolutely clear here. I am not doing any more debugging for you on any live systems. The 1.4.2 (and 1.4.1) plugin is clearly not fit for production use, and as it stands can only be considered as potentially harmful.

    Thread Starter gordboy

    (@gordboy)

    Yes to latest version.

    Yes to access data.

    You cannot of course get to *any* adminer screen unless the wordpress db access data is right, which it has to be since you cannot have wordpress without it.

    Links to screenshots:

    The first is at the “home” adminer page, before any accesses or changes, and shows a minor error event that seems to be harmless –

    http://s24.postimg.org/n7ef13bp1/Screenshot1.png

    The second is trying to “drop” a table, by selecting it and choosing “drop” button –

    http://s2.postimg.org/cgafo0e2h/Screenshot2.png

    Something is still broken. Very broken. The table is not “dropped” and a syntax error is generated. This does not happen with 1.3.2, and I am staying with 1.3.2.

    gordboy

    (@gordboy)

    I think we need a fix for this pretty soon.

    A plugin that creates and/or amends DB entries, that is broken, is no use to anyone. And uninstalling it still leaves the offending posts and postmeta.

    I have tried to contact the author, via Slack, to no avail.

    Thread Starter gordboy

    (@gordboy)

    Thanks for your prompt reply Frank.

    The issue with firebird.inc.php is now cured, but when I try to drop a table I get:

    Invalid arguments passed in ……/wp-content/plugins/adminer/inc/adminer/drivers/mysql.inc.php on line 731

    Syntax error near ” at line 1

    So we are less broken than before, but still broken.

    Also at the foot of the start page I get in red:

    Events

    Access denied for user ‘……’@’localhost’ to database ‘……’

    Which doesn’t seem to affect anything, but should not be there.
    Going back to 1.3.2 again …
    [Pastes edited to remove users, dirs, and db names]

    Thread Starter gordboy

    (@gordboy)

    Nice One

    The update is still working like a champ. And those new features look cool too.

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