New to the community? Start here

Supporter 3 (Pro Blogs) Upgrade Page

0

Hi.

I’d just like to do a +1 on ffdltd’s request to keep version 2’s back-end upgrade page as an option. With Aaron’s answer, I understand the front-end page was highly requested, but I think you can’t force legacy site owners to choose between keeping their back-end upgrade process because it makes sense like this and benefiting from the plugin upgrade with its fancy new features. I don’t say that because I’m in this situation (I’m not) but because it makes sense for me as well to have this process in the back-end.

What I don’t understand though is the issue with SSL certificate for CC payment in the back-end. Is there really no way to do it?

Thanks.

Thu, 18 Aug 2011 23:31:56
  • Aaron
    • Ex Staff

    What I don’t understand though is the issue with SSL certificate for CC payment in the back-end. Is there really no way to do it?

    If you have a subdomain install you need a wildcard ssl cert, which can be pretty steep, a few hundred dollars per year. And that is not compatible with domain mapping, which would cause browser errors.

    Honestly i’d rather have it in the backend as it’s easier to develop for because of the known design. Maybe i’ll be able to add that as a future option.