Hoib

OH!! Amen!!!! Amen!!! Amen!!!

Just 2 minutes ago, I am able to get back in. I looked through wp-config first for those offending lines. Not there. Then, I removed .htaccess completely. Moved it to another folder to get it totally and completely out of the way. Killed the Apache server, not restart services but killed it. Re-launched.

I read where you don’t really need an .htaccess -IF- you simply want to use httpd.conf at a higher level to set up how WP and users will interact with folders below the root.

I am soooo relieved. Now I’ve got to go back in and try to expunge this thing. I did zap all references to IThemes Security Plugins in the SQL database when I was trying to figure out why this happened.

Thank you, Viktor.

H

Oops! OK, sorry…

H

Yes, I did and thanks.

H

OK,I got this now. Thanks for confirming. At localhost, you’re right there’s no issue. I hope I don’t run into this when I go live. I really don’t understand the diff.

And BTW, now I’m facing a huge obstacle. I stumbled and installed this IThemes Security plug-in, activated it and now it 403s and I cannot get back in.

Back to the drawing board.

But thanks for coming in to help me.

H

Yeas, I’m dead too. Can’t even get to the login page on my WAMP/localhost install without seeing:

Forbidden
You don’t have permission to access /wp-login.php on this server.

Apache/2.4.9 (Win32) PHP/5.5.12 Server at volzone Port 80

I’ve moved the plugin folder off. I’ve tweaked the wp-options > backend thing. Restarted the server a dozen times. The result is now always ‘403.

What should I do now besides scrap the whole project and re-do the whole thing?

H

Viktor –

On your fix sequence on the first page/post. Step 2 – rename the folder. You seem to indicate in Step 3 that you should be able to get back to the Admin/dashboard for further treatment (like, never use this thing again…) Anyway I have renamed it, even restarted WAMP and I’m still getting 403’d. I can’t even pull up the log in page.

Do you have any suggestions for this scenario where you cannot get logged back in? Do you think if I continued down your list even though I can’t get back to logging in, this might bear some fruit.

I’m totally locked out. Thankfully I just started to dev this blog so I don’t have a lot of time and data in the project.

Hope to hear. Thanks.

H

I’ve written to the plug-in author. Quick and very responsive I must say! Says he sees the problem and is working on a fix. Stay tuned…
H

WP-Login plug-in. Once deactivated blog turns to sweetness. Activated – blog turns to crap again.

You did it! And it was easy to perform, too.

Looking now for a replacement log-in feature. What’s a good one?

Thank you.

H

No I didn’t. I guess I should take your advice. It’s funny that it happened out of the blue. Let me try that.

H

I have two desktops and one laptop. I’ve narrowed this “no visual editor” to just one desktop. I use IE8 solely all around. So, on the one desktop, I’ve followed all the “tick this on and off”, clear cache, reload browser with F5, go into edit/F5 come back in suggestions. Kill IE and use XP Pro’s Control Panel Internet Options to clear history, cache and cookies. Only on this one machine, it’s broken. It’s unfortunate as it’s my one main machine I use for this. I do not have server level access so no going to take out hta.access.

Question please: Are we able to use another IDE like a Dreamweaver to edit our WP blogs? Anyone tried that? That would get me out of this silliness and on to more important things.

H

Issue is resolved.

I inadvertently and unintentionally wound up “logging in” to the live copy even though I was editting in the local copy. The new version requires the PHP upgrade which the live server does not have. I have no ability to upgrade PHP as it’s not my server. The error is in fact coming from the server, not my local in-house copy as I intended. And, I never realized it until just now.

This fix will have to wait for the server owner to take action.

H

Thank you for you input.
I think this tells me to look to another plug-in for a better formatting “feel”.

H

Hey darthmilhouse

I have the exact same issue with https://svdpexeter.com/photos. You’re right, you cannot simply place text or content anywhere else except at the bottom. Pim Linders recently posted saying he’s not devoting much time now to this project but invites us to stay tuned. Don’t think I’d wait too long.

Have you ever found a solution? Did you move on to another more mature plug-in – one that has instructions to follow?

Hope you’re monitoring this thread.

H

Maybe I can try to explain this better so that someone can tell me if I’m expecting too much from this plugin.

All my “Sets” are showing up “crammed” or stacked up together with no separation. I’d like to separate them on the WP Photos page with some sort of subtitle for each “Set”. Is that possible? If so, how? Is there some sort of parameter you feed to: [flickr_highslide] to have it look at a particular Set so it positions that Set on the page in an ordered fashion? Or do all “Sets” need to be shown as a giant group?

Hope someone can tell me so I can move on…

H

OK, I see. Some questions further:

Where does this “test version” of our system live? On our server? It’s a complete copy of it in your scenario, right? Or does is reside on a /localhost/? If on our server, which isn’t in our direct control, then do we create a “draft” Home Page, hide it, copy/paste, play etc.? I think “test version” implies a complete copy of the pages, right?

Using this concept (which is logical) however she would probably not be able to modify the templates the Theme, the CSS etc. where all the “looks” get done. That’s where most of our work needs to be done, unfortunately.

There’s just no easy way as I’ve been reading up on this. What you suggest is make a copy of the whole thing. I’m looking at modifying more than just the raw page content.

Am I on the right track?

H