• Resolved Rusty35

    (@rusty35)


    I have been using WordPress for several years without really knowing how or why it works, but simply enjoyed the interface and relative ease of making quick and easy updates and changes to the pages from right within my browser. My webhost no longer supports my older version of php without an additional support fee, so I am trying to upgrade to 7.3. I apparently have some other configuration problems which I haven’t the foggiest idea how to fix.

    The page itself will open and display relatively normal (absent an error message at the very top: <<<Warning: Use of undefined constant widget_share_on_facebook_register – assumed ‘widget_share_on_facebook_register’ (this will throw an Error in a future version of PHP) in /homepages/39/d245187759/htdocs/no-coincidences/wp-content/plugins/share-on-facebook/shareonfacebook.php on line 269>>>

    But when I try to login to my dashboard at the <wp-admin> page, I get the warnings below with nothing else, and I am completely clueless what and how I need to fix this.

    <<<
    Warning: Use of undefined constant widget_share_on_facebook_register – assumed ‘widget_share_on_facebook_register’ (this will throw an Error in a future version of PHP) in /homepages/39/d245187759/htdocs/no-coincidences/wp-content/plugins/share-on-facebook/shareonfacebook.php on line 269

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/39/d245187759/htdocs/no-coincidences/wp-content/plugins/share-on-facebook/shareonfacebook.php:269) in /homepages/39/d245187759/htdocs/no-coincidences/wp-login.php on line 418

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/39/d245187759/htdocs/no-coincidences/wp-content/plugins/share-on-facebook/shareonfacebook.php:269) in /homepages/39/d245187759/htdocs/no-coincidences/wp-login.php on line 431

    Warning: Illegal string offset ‘remember’ in /homepages/39/d245187759/htdocs/no-coincidences/wp-includes/user.php on line 39

    Warning: Cannot assign an empty string to a string offset in /homepages/39/d245187759/htdocs/no-coincidences/wp-includes/user.php on line 39

    Warning: Illegal string offset ‘user_login’ in /homepages/39/d245187759/htdocs/no-coincidences/wp-includes/user.php on line 54

    Fatal error: Uncaught Error: Cannot create references to/from string offsets in /homepages/39/d245187759/htdocs/no-coincidences/wp-includes/user.php:54 Stack trace: #0 /homepages/39/d245187759/htdocs/no-coincidences/wp-login.php(770): wp_signon(”, ”) #1 {main} thrown in /homepages/39/d245187759/htdocs/no-coincidences/wp-includes/user.php on line 54>>>

    I have a second page with a similar but slightly different problem – also was not an issue until I tried to upgrade the php version.

    <<< Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /homepages/39/d245187759/htdocs/getpaid/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php on line 77

    Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /homepages/39/d245187759/htdocs/getpaid/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php on line 87

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/39/d245187759/htdocs/getpaid/wp-content/plugins/jetpack/_inc/lib/class.media-summary.php:77) in /homepages/39/d245187759/htdocs/getpaid/wp-admin/includes/misc.php on line 1198>>>

    I am willing to take any appropriate criticisms for my failures. In the past it usually just worked and I knew just enough to be dangerous, but never learned the actual pieces and parts or syntax. So now I am completely confounded and need to be treated like and spoken to as if I were a 5 year old! I probably put too many bell and whistle add-ons or widgets and created some sort of conflict – but as I said, it always worked before I did this php upgrade – or I was at least able to access my dashboard and disable/adjust when I saw that new add-ons weren’t “playing nice” with each other.

    Thanks in advance for any advice or help.

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

Viewing 8 replies - 1 through 8 (of 8 total)
  • Moderator t-p

    (@t-p)

    First, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/plugins/ and delete the share-on-facebook directory.

    Thread Starter Rusty35

    (@rusty35)

    Okay, step one done. It had been several years since I last accessed the site through FTP, so I first had to clear up the hiccups that FileZilla was tossing out at me, but I managed to figure that one out on my own and finally got in and got rid of the pesky share-on-facebook directory. (Thanks for the help, by the way)
    Do you have a step two for the remaining issues?

    Moderator t-p

    (@t-p)

    Okay, step one done. … Do you have a step two for the remaining issues

    Did the the solution take care of issues? If not, What;s the second issue?

    Thread Starter Rusty35

    (@rusty35)

    I’m sorry – yes that took care of the “share on Facebook” widget issue, eliminating that first portion of the error message – thank you; but I still have several other glitches preventing me from logging in to the site to make changes at my /wp-login.php page. I have several different subdomains – each with the exact same errors relating to my user.php file and then I have one other page with a completely different error relating to jetpack.

    I am not tech savvy enough to know what I need to add/remove/change in my user.php code to make the browser happy and give me back access to login.

    Rather than paste the full text errors here, is it okay to just provide the URL links?

    Thread Starter Rusty35

    (@rusty35)

    Update: I “think” I’ve fixed my other page’s problem with the jetpack error. I regressed the php version back to 5.6 and was then able to gain access to my WordPress dashboard – which showed a failed update that needed to be run again. Page was ‘down for maintenance’ for a few minutes, but now it appears to be back up and running with :::knock on wood::: no problems (fingers crossed).

    So I just have the remaining issue with my user.php that appears on my other pages’ login screens.

    Thread Starter Rusty35

    (@rusty35)

    I found this article, which sounds like it is identical to the problem I am experiencing. I haven’t had the chance yet to apply this solution to my sites (life + a regular job getting in the way!) but I hope to give it a shot sometime this week when I have some free time.

    Thread Starter Rusty35

    (@rusty35)

    Yep, that was it. I had to manually update WordPress files to the latest version.

    Moderator t-p

    (@t-p)

    Glad to know it 🙂

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Complete novice with no programming or coding knowledge – fouled up my pages’ is closed to new replies.