thinbluesmoke
Forum Replies Created
-
Forum: Everything else WordPress
In reply to: Suspicious MailCatch RegistrationsAwesome!!! Thanks for the links Steve and Luke. Looks like I should be able to prevent trouble before it starts. I appreciate it!
Forum: Everything else WordPress
In reply to: Suspicious MailCatch RegistrationsThe thing is, none of these users with the mailcatch addresses are leaving any comments, they’re just registering and moving on. That’s what had me concerned.
Forum: Everything else WordPress
In reply to: Suspicious MailCatch RegistrationsOnly registered users can submit comments.
Forum: Everything else WordPress
In reply to: Suspicious MailCatch RegistrationsOK, thanks. I was more or less wondering if anyone else has seen a trend of mailcatch registrations and if it meant anything unusual.
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installOk, it looks like I’m back in business as far as the blog home page loading. I contacted my web host and they changed the URL path and my blog home page loads from the web root name; https://MySiteName.com. I have no clue where they made the change or what it was changed to but I assume it resolves to the WordPress directory.
That part of the mission is accomplished but my one and only post won’t load when clicking the link. I remember seeing a note about this is the instructions for changing the web root location. I’ll see what I can do and if I have any further issues I’ll create a new topic here at the forum.
Thanks Mark for riding this one out with me.
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installOk, Before I do any further damage I think I’ll submit a support ticket to my web host to see what gives. I honestly don’t know how that URL resolves to my WordPress blog when the folder hierarchy is so convoluted. What you’re suggesting makes perfect sense to me. Thanks!
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installHey, I just noticed something. There’s a .htaccess file under /webspace. It’s evidently protected because it won’t let me view or copy. I wonder if that’s got anything to do with all this???
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installBy the way, shouldnt you be checking what’s in /webspace/httpdocs/thinbluesmoke.com/ ? That’s where WordPress is looking for the files..
That’s where I copied the index and htaccess files. Originally it was some default HTML that displayed some page the host came up with.
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installDid you see my screenshot? https://www.flickr.com/photos/29329161@N08/26888258846/
I’m on a shared hosting plan and I essentially “auto-installed” WordPress via a utility. I assumed that they renamed the WordPress folder to WordPress-60594 for some reason that helps them keep track of things. The hierarchy is there that you pointed out.
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installHere’s a screenshot; https://www.flickr.com/photos/29329161@N08/26888258846/
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installThat was the URL to get to my WP blog via a browser.
I’m looking at the folder structure with FileZilla and it shows the path to wp-blog-header.php as; /webspace/siteapps/WordPress-60594/htdocs/wp-blog-header.php
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installThat file is in the htdocs folder
WordPress-60594/htdocs
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installI actually did that initially per the instructions. I just tried it again to no avail. Then I tried the actual file path.
I get this;
Warning: require(/usr/local/pem/vhosts/121764/webspace/httpdocs/thinbluesmoke.com/wordpress/wp-blog-header.php): failed to open stream: No such file or directory in /usr/local/pem/vhosts/121764/webspace/httpdocs/thinbluesmoke.com/index.php on line 17 Fatal error: require(): Failed opening required ‘/usr/local/pem/vhosts/121764/webspace/httpdocs/thinbluesmoke.com/wordpress/wp-blog-header.php’ (include_path=’.:/usr/libexec/php4-cgi/share/pear’) in /usr/local/pem/vhosts/121764/webspace/httpdocs/thinbluesmoke.com/index.php on line 17
Forum: Fixing WordPress
In reply to: Problem: Using a pre-existing subdirectory installI apologize, I said that I moved them. I did not. I copied them. It’s been a long day.
Yes, I performed step 2