metakong

Mvied, I’ll kick ya’ a donation once revenue is rolling in to say thanks for being an upstanding kat. I would still, ideally, like to see a little more documentation. But, from what I can tell, you do quality work. Thank you much for that.

Thanks, Ipstenu and Mvied, for the replies guys.

My caching plugins/options have not been set yet. I’m no tech expert, but I’m no dummy either, caching won’t be set until I’m 100% production ready for launch.

Good to know re: generally accepted plugin behavior. At the moment, it was all I could think of for the continued rewrite.

RE: rewrite_rules db entry, I would assume that was WP doin’ the rewrite biz upon install or plugin option saving.

RE: Feedback for Mike’s valiant improvement and follow through – My bonehead mistake was forgetting that 443 is the default SSL port and setting the incorrect port.

Makes me feel like a douchenozzle admitting it publicly, but it will force me to give your plugin another shot now that I know.

Maybe a simple note on the options page re: port selection would be good for people like me with more bullocks than brains would be good, something like “The default ssl port for most hosts is 443.” Or, perhaps a friendly reminder to check with your host for their default SSL port.

The two above would be the immediate simple solutions prior to implementing some idiot proof system that stops “go-getters” like me from setting options to quickly without thinking.

Thanks again for the follow up guys.

Answer:

Log into your database GUI or via ssh

out of wp_options in your wp database, navigate to your newest entries and delete anything that starts with wordpress-https AND the entry titled rewrite_rules.

Follow up:

As expected: lack of documentation.

This is infuriating.
I haven’t looked yet. But, I have a funny feeling I won’t find the answer I’m looking for pre-loaded in an FAQ anywhere.

Dear Plugin Authors,

What wordpress files does your plugin alter so I can manually change them all back to defaults prior to installing your plugin and subsequently regain access to my f’n admin panel.

The GUI will throw errors while actually writing the changes it states it refused to write, very nice. Those changes obv stay in place after your plugin is deactivated (it took me 30 seconds to realize this thing was unneeded and not nearly as valuable as 50 -5star ratings seems to imply) and deleted, but the changes it made it those 30 seconds now have all my admin pages redirecting to a non existent port on my domains server.

Whoever can tell me exactly what files/functions/methods/hooks I need to remove to get back to where I was 5 minutes ago would be my hero. Until then I can’t do sht on my site until I figure it out and I don’t feel like digging through every f’n php file in my server to figure out what havoc this little doosie has managed to wreak in under 5 minutes.

FTP into your site (or use whatever file management application your host provides) and delete the wp-content/plugins/wordpress-https folder.

Not exactly. Can’t access anything. Even after delete.