Support » Plugin: Transposh WordPress Translation » Error message: Cannot use object of type WP_Comment as array

  • Hello

    My site was working perfectly with the plugin but suddenly I beggin to have the followin error and now, its innacesable:

    Error Details
    =============
    An error of type E_ERROR was caused in line 967 of the file /**/**/public_html/wp-content/plugins/transposh-translation-filter-for-wordpress/wp/transposh_admin.php. Error message: Cannot use object of type WP_Comment as array

    The requested line shows the following;

    $actions[‘language’] = __(‘Language’, TRANSPOSH_TEXT_DOMAIN) . “(comment_ID}\” data-lang=\”{$comment_lang}\” href=\”\” onclick=\”return false\”>$text)”;
    return $actions;

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • You might want to disable Transposh (renaming wp-content\plugins\transposh-translation-filter-for-wordpress\ in your WordPress directory) to make your website work again, by using your hosting panel’s file manager, SFTP or such:

    https://duckduckgo.com/?q=wordpress+plugin+crashes+rename+directory

    Afterwards, you can try to search for the error to find a solution (can’t find another occurrence with Transposh though), try reinstalling Transposh (backup your DB first, preferably), deactivating other plugins to find a conflict, or undoing any recent changes.

    Good luck!

    Plugin Author Ofer Wald

    (@oferwald)

    Hello,

    I agree with @chemaz regarding the way to go, first make sure that your site works

    However, we have no reports of such error, and something probably have changed so this will happen, any information regarding this will help us resolve this quicker

    Good luck,

    Hello
    Thanks for your help.
    I already rename the plugin folder, however, Also disable all the plugins using phpmyadmin but the site still dont work.
    I cant accest to the wordpress dashboard neither.

    Plugin Author Ofer Wald

    (@oferwald)

    Hi,

    Do you still get an error from our plugin after renaming the directory? This does not make much sense, as after renaming (hack, even just delete the plugin directory) the code should not be accessible.

    My guess is that there is something elsewhere not properly configured.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.