pam

Hmm, that didn’t work. But my client changed his mind so we can consider the topic closed. Thanks for replying!

You’re my hero! Many many thanks!!

@iainpurdie Thanks! Good info for next time. I have to admit I didn’t click that link assuming it would be a “stock” article that wouldn’t help me with specifics. I shouldn’t assume anything!!
BTW, I edited my post to say I got it going again.

The one time I didn’t test my plugin updates on a cloned site… UGH!
Mine crashed to the point where I cannot access the WP dashboard.

I’ve tried renaming the plugin file via SFTP. I’ve tried deleting that plugin file. I’ve tried replacing it with the 4.7 version. I still get the error code and can’t access my site or the WP dashboard.

Am I missing something? I’m only editing the …wp-content/plugins/add-search-to-menu folder

UPDATE: Figured out a small error on my part which was keeping the changes from working.
RENAMING worked. Then I commented out line 151 as suggested and restored the folder name. That allowed the search feature to work without the crashing.
PHEW! Thanks to everyone for posting suggestions!!

• This reply was modified 3 years, 4 months ago by pam.

version 5.6.2

And I checked to see my formatting. I was using #EVENTPRICEMIN
I switched it to #EVENTPRICERANGEALL and it fixed my issue.

Thanks! I figured it would be simple, just didn’t see it!

As a follow up for people who are curious:
I had to re-install everything in my desired directory and saved most of it through import/export. I think I had three issues – which started to cross-pollinate, so to speak.

1. I originally wanted my wp files in a non-root folder, but my home page in the root folder. I may have confused the “site” and “home” definitions.

2. I had a page called “blog”. But the folder my wp files were in was also called “blog”. So when looking for https://www.mysite/blog it could have meant my wp page OR my ftp folder, causing a problem for the browser looking for that url.

3.I had a screwy plugin. It wasn’t screwy when I started the migration. But in the midst of all this, when I had a glimpse of my dashboard, there was an update available – which I thought might help. That update screwed up websites all over the world.

Oh brother, that’s embarrassing. I was looking everywhere but the obvious and even trying to change it by ftp. Thanks!

THANKS for the quick response! I think I can make the needed adjustments now!

By the way, line 17 of my ..blog/index.php file is:

require( dirname( __FILE__ ) . ‘/wp-blog-header.php’ );

I have now tried to revert everything back to the /blog directory.
I renamed all the wp files in my root to “hide” them.

I can get into the admin panel, and I’ve turned off the maintenance mode. The site url and home url are both pointing to /blog.

Everything works except I can’t visit my site. It should be available at
https://manabeads.com/blog

I get the following error involving the index.php file. Maybe that’s where the error is? I changed that once when I was trying to direct to the correct folder…

Warning: require(D:\Hosting\7741694\html\bloghttps://www.manabeads.com/wp-blog-header.php) [function.require]: failed to open stream: Invalid argument in D:\Hosting\7741694\html\blog\index.php on line 17

Fatal error: require() [function.require]: Failed opening required ‘D:\Hosting\7741694\html\bloghttps://www.manabeads.com/wp-blog-header.php’ (include_path=’.;C:\php\pear’) in D:\Hosting\7741694\html\blog\index.php on line 17

1. No, it was mostly html
2.Yes, the site includes a shopping cart that uses a database, but I believe it’s a separate SQL server db, not the MySQL
3. The live site is at example.com; wordpress was installed on example.com/blog. I moved the files from ../blog to the root according to the directions (at least I thought I did it accordingly), but never installed wordpress a second time.
4. After copying the files, I did not create a new database. I backed it up once I couldn’t login so I could go in and verify the site url, but no new db was created.
5. n/a since I didn’t create any new database.

Also, the WP site was running great from ../blog. The plan was to get the content all completed and then make it my “index” page, redirecting old files to the new WP pages.I kept it in a “maintenance mode” while I worked on it and tested it live every day. I thought maybe the plugin was an issue, but I was able to get on the admin panel that one time, so I don’t think that’s it.

(Thanks for helping)