walkrrrr

I may have to resort to that, but it would be nice if WordPress would just let me in when I enter the VALID username and password.

Yesterday, I finally got in after entering the exact same info and getting an error message about 60 times. Once I was in, I took a screen capture of the profile page, so I know for a fact that I am remembering the info correctly and yes, I *am* entering it correctly.

However, I am still locked out.

Sorry to say that WordPress sucks, from the overwhelmingly negative experience I have had with it at every step of the way. Good thing it’s free.

moserengineering, exact same problem here and WordPress “help” forum mods closed my post before any responses could be made when I posted yesterday asking about this problem.

I’m also locked out, even after FINALLY being let in to my account yesterday upon entering the exact same VALID username and password about 67 times and getting an error message. I had even made a detailed set of notes on how to get in to my account, so I wouldn’t have to go through this again, so I KNEW my username and password were correct. Took a screen capture of my profile page and everything once I was finally in, and yes, I *AM* remembering this info correctly AND entering it correctly but I’m locked out again today.

All I can say about WordPress is, you get what you pay for. No surprise that it’s free because it’s buggy as all crap and has been nearly impossible for me to use no matter what I’m trying to do with it.

No plugins. So far so good w/the 2nd choice template, but I may try Customizr again now that I’ve got the installation straightened out.

Chap, it seemed to have something to do with the memory allocations of my hosting plan, which they made manual adjustments to, then recommended using a different theme to avoid further issues. But thanks for your “input”.

Apparently my reply disappeared…

Thank you for the response, it was a combination of problems. That was part of it, also the reset password email was taking 15-20 minute to arrive each time so I thought I was entering an incorrect email or that it was being blocked for some reason, as I did repeatedly check the spam folder.

Resolved now, thanks again.

Thank you chappie! I will try that w/the next theme I try to use.

rdellconsulting, never mind. The theme was dysfuncional according to my webhost and broke my whole site so I had to uninstall WordPress and start back at the begining. Hoping the next theme I choose won’t break it all over again because I’ve spent about 14 hours so far on the *fabled* 5 minute install. Too bad, because it would have looked nice.

After yet another chat w/webhost, got that resolved, and page now shows the default blog index, saying it’s set to “2013” theme. Now back to the drawing board to see if I will be able to customize it this time.

OK, finally some improvement. Via my hosting account I was able to copletely uninstall and then reinstall WordPress.

However, now when I go to what should be the login URL for the admin settings panel, (https://mydomain.com/wordpress/wp-admin) to try *again* to customize it, there is no way to log in. It’s just the default “Hello world” blog page w/no login or admin access area. WTF now?

OK, another chat w/webhost tech support who says the theme is unusable and I will have to contact the developer pf the theme and have them explain why it’s causing the issue. Apparently I will now have to uninstall WordPress (for the 2nd time over the last 24 hours) and start back at the very beginning again. With some other theme which will hopefully not break my site.

I can’t actually log out because the URL gives me nothing but the error message. Tried in a different browser and get same error message. Back to my webhost tech support…

I did, and was able to get Customizr to work for a few minutes (after a lengthy tech support chat with my webhost who had to manually change some settings in order to resolved the WordPress errors I was getting).

Made some changes, saved and published. Closed the window, now when I try to go to the site again I get the error message.

FYI, I did finally get Customizr installed w/the help of my webhost, but now get the error message after leaving the page for a few minutes and attempting to load it again.

Just for general amusement and because I have nothing else to do with the rest of my life, here is the latest “helpful information” (error message) I get when attempting to access the 14 hours in the making WordPress installataion on my domain:

Warning: require_once(/hsphere/local/home/domain.com/wp-content/themes/customizr/parts/class-header-header_main.php): failed to open stream: No such file or directory in /hsphere/local/home/domain.com/wp-content/themes/customizr/functions.php on line 207 Fatal error: require_once(): Failed opening required ‘/hsphere/local/home/domain.com/wp-content/themes/customizr/parts/class-header-header_main.php’ (include_path=’.:/hsphere/shared/php53/share/pear:/hsphere/shared/apache/libexec/php53ext/php/’) in /hsphere/local/home/domain.com/wp-content/wp-content/themes/customizr/functions.php on line 207

Thank you. My webhost had to go in and manually change some of the settings on their end in order to get WordPress to install properly. At least for a few minutes. Now that I closed the page and tried to visit the URL again I get a new long meaningless string of error syntax.

Back to Square One apparently, with another 15 hours to be spent on the “5 minute setup”.

Or maybe not. Now that I left the page for a few minutes, I get nothing but a long meaningless paragraph of error syntax when I make the foolhardy and naive attempt to visit the URL again. Maybe if I wait another few hours and try a few different browsers, reset my password several times and chat with my webhost tech support dept. for another hour or 2 they will be able to do something to make the “famous 5 minute setup” function properly again for a few seconds.

Meanwhile, I will try the Customizr forum, on the theory that at some point in time I will actually be able to load the partially configured page again without getting yet another error message.