dgebel
Forum Replies Created
-
Forum: Plugins
In reply to: [Audio Player] [Plugin: Audio Player] Is this a HACKED version??1. Everything on the plugin site for this plugin is an exact duplicate of the other plugin, which is ALSO called “Audio Player”, down to the version numbers. Just do a search from the dashboard for Audio Player.
2. The name has been changed of the zip archive and the path must have been changed too.
3. The size is different, but all the files inside are the same size – it may only be the difference in the file path that makes the archive size different.
4. It doesn’t work upon install. It MAY work if you correct the path to the plugin in the Settings area.I had just been noting some of the security alerts – I may have over-reacted to a badly configured archive :-}
But it seems very odd that the author would create another plugin entry and do nothing but change the name to a nonsense name and then do it wrong. I’m wondering if his account was one of those that got hacked but nothing was ever done with it and then all the passwords were reset.
Mike, yes it was 2.02 – I created an id for you and you should have received the welcome email. Let me know if not.
I can confirm the results Bozz is getting, same on mine, but I’m not using an add-on domain (yet), just a folder in my main directory.
Not sure about individual pages yet.Works as long as you don’t Force SSL in admin. Then you get the odd doubled account name/redirection effect.
I finally found version 1.92 – it seems to work fine. Better than I expected actually, since it does a redirect and thus no red address bar to scare someone.
I am willing to be a test site for version 2.0 updates.
By the way, about my last comment. That’s if all the Force SSL options are off. If I switch any of them on, I get 404s when I try to go to the page.
Not to hijack, since this seems to be a finished subject now, but I’m having the same problem. See http://wordpress.org/support/topic/plugin-wordpress-https-ssl-not-working-for-shared-ssl-on-bluehost?replies=3#post-2450483 for details.
Yes, I’m using the Shared SSL.
Sorry, the point in my list above where I mention the secured host is starting to refer to entering items on the WordPress-SSL settings panel.
I.e., I put “secure.bluehost.com/~example” into the “SSL Host” field on the WordPress-SSL settings panel.
bh_WP_fan, do you mean I have to change the Site URL to “secure.bluehost.com/~example/testsite” ? I believe I saw something about that setting somewhere, but… that would use SSL for the whole site, right? I just want to secure a few pages, particularly the login although all of admin is ok.
It looks like this plugin is supposed to allow one to secure all pages or just pages you force to use SSL (the exclusive checkbox), and separately secure (or not) the admin area. I don’t want visitors to use SSL. (I wish BH let us get certs for addon domains for a store, though).
Incidentally, as per another thread, I tried setting permalinks to default. It didn’t make any difference.
WP really should be renamed that option, because “Default” was not the default!
I looked at the other post, but he just says it started to work with v1.92 – which I can’t seem to find anywhere.
When I got to https://secure.bluehost.com/~example/testsite the pages are displayed that same as if it was http – nothing has been secured anyway. If I try to log in, I get a red address bar and nothing happens, ie login doesn’t work – there’s no error message or anything, the form just clears.