robbart

Ah, ok, well that’s a start… That does describe what is happening. That is, it’s only resetting the theme sporadically, and NOT when I am in the admin area.

Thanks Otto.

It would be nice if WP logged these sort of events, so at least we could investigate the cause, instead of guessing and having nothing to research or go on.

bump

I am using themes that were downloaded from the theme gallery; I haven’t created my own.

They appear to have the correct info at the top, like this one:

/*
Theme Name: Journalist
Theme URI: https://lucianmarin.com/
Description: Journalist is a smart, minimal theme designed for professional journalists.
Version: 1.9
Author: Lucian E. Marin
Tags: white, two columns, fixed width, light, minimal
For the WordPress community (GPL), enjoy it guys.
by Lucian E. Marin – lucianmarin.com
*/

Some further information.

Even though the public view drops the theme I chose, and shows the default theme for some reason, in the admin, it still shows the theme I have selected as the them that has been activated.

I agree that it is probably impossible to update WP to use MS SQL TODAY. Every plugin currently depends on that DB, so they would all have to change as well. This is not a simple matter of modifying some SQL statements in the WP files, but all the plugins, etc as well.

WP is in this predicament because it wasn’t designed to have the database access abstracted out. If WP were MY product, I would make all DB access go through a plugin, a “data access layer”. You would then theoretically have a plugin for MySQL, MSSql, etc. Why be limited by the backend?

Anyone making statements comparing MySql to MS SQL should have their facts straight before doing so. While I am certain that MySql is solid, I don’t know that the evidence suggests that on a larger scale, it handles the scalability that SQL Server does. Or even Oracle. Fact is, if I had my druthers, I’d prefer an enterprise level backend for several reasons. But the primary reason, is that in some cases, you don’t have the option of tossing MySql on a production server next to Sql Server. That would never be allowed where I work. As much as I like WP, I would just have to find another solution. It seems that the WP community should be looking to add new instances of this tool, not eliminate them by saying …

WordPress requires MySQL. Plain and Simple.

You want to use MS SQL, find an ASP solution, or rewrite the entire program.

That’s a poor response in my opinion.

So, while I have agree with the overall sentiment, that it doesn’t support MS SQL, I have to disagree that it’s a losing proposition supporting other DB’s.

In addition, if the div is intended to surround the page content, it needs to start in one file (header.php) and end in another (footer.php).

You can simply move all of your wp files into your webroot.

As long as you only have relative links to images, etc. (no hardcoded links), it should work just fine.

However, if what you want to do is leave the files in the subfolder where they are now, and have https://www.mydomain.com point to that folder, your webhost will have to change your webroot folder to point to the wp folder. It’s nothing major really.

Ok, well after having no responses, I just played around a bit… and after posting a change from my Theme options page (added a new widget to the sidebar), the text on the site just magically showed up.

If there is any information that could possibly assist in making a suggestion, just let me know.

As of now, my blog is empty.

As an aside, on the same VPS, I am running another wp blog. Xferred it the same way. It’s all good; no issues whatsoever.

According to the Gallery2 FAQ (https://codex.gallery2.org/Gallery2:FAQ)

How can I fix the filesystem permissions of the Gallery storage folder?

Usually you get either an ERROR_PLATFORM_FAILURE or the upgrade wizard reports that the filesystem permissions are wrong for your storage folder, i.e. it can’t write to all files and subfolders in that folder anymore.

* To fix the problem, you can try the Fix the storage folder (make it writeable) tool in https://example.com/gallery2/lib/support/ on the Filesystem Permissions page. (This tool was added in G2.1.1), older versions don’t have it.

* You can also try to change the permissions to 777 (read & writeable for everyone) with your FTP program. If all fails, please ask in the forum for help such that we can verify that it is indeed a filesystem permissions problem. If it actually is one, you’ll have to ask your webhost to change the filesystem permissions recursively for you (e.g. chmod -R 777 g2data).

* What might help is removing all cached data from the storage folder. Please see: How can I clear cached data?

* A common issue is:

Error (ERROR_PLATFORM_FAILURE) :
in modules/core/classes/GalleryTemplate.class at line 270 (gallerycoreapi::error)
in modules/core/classes/GalleryTemplate.class at line 200 (gallerytemplate::_initcompiledtemplatedir)

In that case, if the above suggestions do not help, please try to delete g2data/smarty/templates_c/ folder via FTP or whatever tool you use to upload / manage files of your website.

* If the problem does not disappear or is reappearing after it has been fixed for a while, please ask your webhost whether there are any scripts that change the owner of the files to the account owner. This could be the culprit since files are not created / managed by your account, but by the webserver application. We also welcome you to consult the Gallery forums for further expert advice.

Surely, someone has some inkling of an idea?

1) It only means that both instances of your Blog are using the same database information. Your mysql db is accessible from any application with your username and password. It’s not restricted by path or file.
2) Why did you do this?
3) Unless you want it running this way, I would recommend removing one of the two instances. If you want to go to https://oceanboom.com/ only to get to your blog, and not https://oceanboom.com/OCB then I would remove https://oceanboom.com/OCB altogether. Or vise versa if you want the OCB stuff. You will need to put a default document or other stuff up there after you do that.

WordPress is software. It is intended to be run by itself, as a stand alone web site.

However, using frames you could do what you are suggesting.

You do need to have some technical proficiency with HTML for this to work.

Ah well that’s part of your problem. You need a windows FTP client.

There are a few out there. A quick google netted me a bunch.

You might wanna try

FTPSurfer, FREE, https://www.whispertech.com/surfer/

For a commercial program, try WS FTP, https://www.wsftp.com/

Just google “Windows free FTP client”.