• Resolved LSBK

    (@lsbk)


    Hi
    I cannot load the dashboard (login is possible)

    I get this messages:

    Ein Fehler vom Typ E_ERROR wurde in der Zeile 27 der Datei /home/lesbisch/www/lsbk.ch/wp-content/plugins/backwpup/inc/functions.php verursacht. Fehlermeldung: Uncaught InvalidArgumentException: Cannot locate the template /home/lesbisch/www/lsbk.ch/wp-content/plugins/backwpup/views/notice/notice.php in template function. in /home/lesbisch/www/lsbk.ch/wp-content/plugins/backwpup/inc/functions.php:27
    Stack trace:
    #0 /home/lesbisch/www/lsbk.ch/wp-content/plugins/backwpup/inc/Notice/NoticeView.php(47): backwpup_template(Object(Inpsyde\BackWPup\Notice\NoticeMessage), '/notice/notice....')
    #1 /home/lesbisch/www/lsbk.ch/wp-content/plugins/backwpup/inc/Notice/NoticeView.php(104): Inpsyde\BackWPup\Notice\NoticeView->notice(Object(Inpsyde\BackWPup\Notice\NoticeMessage), NULL, 'notice-warning')
    #2 /home/lesbisch/www/lsbk.ch/wp-content/plugins/backwpup/inc/Notice/DropboxNotice.php(29): Inpsyde\BackWPup\Notice\NoticeView->__call('warning', Array)
    #3 /home/lesbisch/www/lsbk.ch/wp-content/plugins/backwpup/inc/Notice/Notice.php(112): Inpsyde\BackWPup\Notice\DropboxNotice->render(Object(Inpsyde\BackWPup\Notice\NoticeMessage))
    #4 /home/lesbisch/www/lsbk.ch/wp-includes/class-wp-hook.p
    

    After renaming the folder I can work without the the plugin…

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support happyAnt

    (@duongcuong96)

    Hello @lsbk
    Please try to update again, it should work, thank you!

    Thread Starter LSBK

    (@lsbk)

    Hi
    I had to delete all the files in the plugin folder and to reinstall backwpup from scratch. Then I could redo the Dropbox authorisation.
    Now it works again.

    Plugin Support happyAnt

    (@duongcuong96)

    Hello @lsbk
    happy to hear that all works ^^
    Please let us know in case you have any other issue ^^

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Problem with 3.10.0 after upgrade’ is closed to new replies.