wpadminvic

Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Forum: Fixing WordPress
    In reply to: SSL certificate confusion
    Thread Starter wpadminvic

    (@wpadminvic)

    3 years, 11 months ago

    Both the php files checked out – no hard-coded urls.

    However, while scrutinizing the DB, I noticed that all the posts and uploaded images have GUID of HTTP instead of HTTPS.

    Also, the blog allows visitors to write to the author, and all the messages have a source_url that is HTTP: in the database. These contacts can be deleted in bulk, and most of them are spam anywawys.

    Could this be keeping the URL setting greyed out, because of the dependencies with hard-coded paths?

    Forum: Fixing WordPress
    In reply to: SSL certificate confusion
    Thread Starter wpadminvic

    (@wpadminvic)

    3 years, 11 months ago

    Thank you both!

    WordPress admin page’s “Settings > General Settings” WordPress Address (URL) and Site Address (URL) are greyed out to prevent editing, so I updated the _options table in the database to change siteurl and home to use https://

    However, upon reloading the WordPress admin page, it would still show http:// in the greyed out setting. There are some posts that states wp-config.php can overwrite the setting, but I don’t see any overwrites in that file.

    Does WordPress need to be refreshed, or is there another overwrite somewhere in the file structure that points to http:// that overwrites the database records?

    Forum: Fixing WordPress
    In reply to: Fatal error with substrate plugin; 500 error; admin panel inaccessible
    Thread Starter wpadminvic

    (@wpadminvic)

    7 years, 3 months ago

    The website is up and running – renaming the entire substrate directory would break the website, but renaming the following file worked:

    /www.mysitename.com/web/content/content/mu-plugins/substrate/modules/utilities-link.php

    to

    /www.mysitename.com/web/content/content/mu-plugins/substrate/modules/utilities-link.HOLD.php

    Forum: Fixing WordPress
    In reply to: Fatal error with substrate plugin; 500 error; admin panel inaccessible
    Thread Starter wpadminvic

    (@wpadminvic)

    7 years, 3 months ago

    It would appear that the /web/content/content/mu-plugins/ directory is a platform add-in that does not have permissions to change on any level.

    However, I do have the permission to rename the /web/content/ directory.

    I am proposing the following:

    1. Rename /web/content/ to /web/content.OLD/
    2. Copy /web/content.OLD/ to local drive
    3. Rename the /web/content/content/mu-plugins/substrate/ directory to /web/content/content/mu-plugins/substrate.OLD/
    4. Copy /web/content.OLD/ from local drive to network as /web/content/

    The new /web/content/ would have the /web/content/content/mu-plugins/substrate.OLD/ directory.

    Forum: Fixing WordPress
    In reply to: Fatal error with substrate plugin; 500 error; admin panel inaccessible
    Thread Starter wpadminvic

    (@wpadminvic)

    7 years, 3 months ago

    Thanks Jarret – yes I do have access to the files since I have admin access. I will try to delete folders via SFTP, after making a full backup of the site.

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