wpcdn

Would also love to know.

Clarify…I mean the site DOES show the normal browser window titles, but these are not the ones I’m talking about.

My experiences have been quite positive. This plugin has been a lifesaver.

Although free always seems better, Naomi has clearly put a lot of work into this plugin. And for many people it removes the need to buy a Gravity Forms Developer License. All in all, this is a commercial-quality plugin that eliminates a $199 purchase. (Indeed, the Gravity Forms Developer License seems well worth the money. But, for people who only need to add Stripe to a website, this is a bargain.

I donated a few weeks ago, and the support from Naomi has been fantastic. I had a couple of small issues which were resolved quickly. I also requested a feature, and it was added to the next release of the plugin within a few days.

People have to eat, and I definitely feel that my donation was well worth the money spent, several times over in fact.

Mark

Hi Mike

So far everything seems to work with the new version.

I am noticing that SSL login seems to take a long time. Is that normal, or is there any way around it?

I’ll keep testing and let you know if I experience any other issues. But so far it looks good.

Thanks for your hard work and continued efforts on this.

Mark

Hi Again,

I deleted and reinstalled WordPress, and the plugin is working…EXCEPT:

Uploaded images still have the wrong URL. It’s still https and uses the SSL hostname instead of the front-end hostname.

Example:

https://anothertry.wpcdn.com/?p=1

The memory graph still has the problem URL.

Sorry!

Mark

Update: I realized that in the re-install, the hostname had been reset to default. So that might explain the behavior mentioned in my post above.

However, now I can’t set the hostname. When i use the same hostname I was using before, I get the error that there is an invalid WordPress install at that host.

Not sure what to do…

Thanks,

Mark

Hi Mike,

I re-installed, but the new version doesn’t work for me. The admin login page CSS is gone (the ugly bare-bones form instead of the styled form).

Then, when I try to login, I just get a 404.

This is on the same site that was working prior to this update.

Thanks,

Mark

Hi Mike,

I think the media URL is a problem. That URL does seem to be permanent, for example look at this post:

https://anothertry.wpcdn.com/uncategorized/hello-world/

The uploaded image (the metallic WordPress logo) has this URL:

https://host1.wppronto.com/~anothert/wp-content/uploads/2012/02/wp-logo.jpeg

…which is undesirable for aesthetic reasons, and because it can mess up caching and CDN plugins that expect the public domain name instead of the special SSL hostname.

I know that this could be manipulated by hardcoding the wp-config file…I think something like:

define(‘WP_CONTENT_URL’,’https://wpprontocdn/wp-content’);

But we don’t want our novice users to have to do things like this. So is there any way the plugin could do that and keep uploaded media with the desired public URL instead of the special SSL URL?

Thanks,

Mark

Hi,

I’ve tested on another site on the same server, and so far I’m not seeing those problems again.

We are using a Varnish proxy, but that shouldn’t apply because it passes all wp-admin requests directly to Apache. Should we leave the proxy setting “Off”?

I am seeing another issue: if you upload media while logged in via the special HTTPS hostname, the URL of the uploaded media is in the format:

https://host.ssldomain.com/~username/wp-content/uploads/2012/04/image.png

Of course, it should ideally be in the format:

https://sitedomain.com/wp-content/uploads/2012/04/image.png

In other words, media URLs should take on the front-end domain name instead of the special (shared SSL certificate )hostname.

Any way around this?

Thanks,

Mark

Hi,

On first test, I see two issues:

1) The settings aren’t saving the hostname. In this case, it’s a blog in a subdirectory, so the hostname is:

domain.com/~username/subdirectory

However, it always reverts to:

domain.com/~username

And when I try to login via HTTPS, I get the same redirect loop I had before (possibly related to the item above).

I’ll keep testing and let you know.

Thanks,

Mark

Hi Mike,

Sure, I’ll try that and let you know. I’ll be happy to show you the site if it’s still not working.

Mark

>> Why fix what isn’t broken?

There were issues with the previous version for some people. For example, on our servers there is an endless redirect loop that makes the previous version unusable. So I applaud Mike’s efforts.

Mark

Cool, thanks!

I’ll test promptly when the fix is available.

Mark

Oh, if you were asking if the front-side pages of the blog work via SSL and that address, they do but the CSS is missing too (as expected).

Mark

Hi,

The problem is that I can’t get logged in via SSL. For example, I go to:

https://hostname.domain.com/~accountname

…and hit the login button, there is then a 404 because the browser is trying to go to this URL:

https://hostname.domain.com/~accountname/~accountname

Also, when I go to the login form as mentioned above, there is no CSS (Just the ugly unformatted form)…in case that’s relevant.

Thanks,

Mark