Dan Cole

Gary, I assume you mean withOUT a core code change? Dan

I have those working and have prettied them up over the years and while they are all individual modules the routine to do accomplish that is hacked into the index page as I recall. At some point I might rework them so they are of use in Phoenix, if and when I ever get the time to look at the admin side of my shop. It certainly won't be anytime soon. Dan

@ArtcoInc Sorry Malcolm I'm not going to be of much use to you on this. My admin is still running on RC2. I've made so many hacks to the core on the admin side of my shop over the years that I'm not sure where to start (not really) and it has a real low priority for me. Dan

As a wise person once said.... If you are not part of the solution, you're part of the problem. Dan

No one should be upset by that. It is a good thing. Shop owners and developers just need pick the version they want to use or support and go from there. You don't need to follow every update as some seem to be doing and then complain to developers that add-ons are broken. Dan

I would, at least start working on updating. Frozen is getting a little long on the tooth and is sun-setted. If you're relying on any add-ons using 1.0.5.0 might be your best bet. I would land there and once you get that as you like....launch it and then begin updating beyond that. Dan

For me that is both fair and realistic. I have add-ons I can't live without and until they are updated the choice is update or keep those functions. My current plan is to get a live site up and running 1.0.5.0 (I'm close) and then keep a development branch going that I can add updates to, both core and add-ons. Taking that to say 1.0.6.0 and when it's ready to release, I'll rinse and repeat. Until the add-ons get to a point where they are not impacted by changes to the core I don't think it can be managed in any other way. If there is, I'd certainly be interested in knowing. Dan

You don't have to update but it is a good opportunity to see the latest developments, what is planned and the support that is offered. You'll also ensure that any requests you have for help are seen by those who can help. Many of them are no longer active in the open part of this forum, or at least don't frequent it as often as they once use to. Dan

I think there is one in the Phoenix Club where you can show your gratitude. 😀 Dan

Just noticed an unusual behavior when adding a coupon code on my Phoenix build 4.2 I'm using Discount Codes version 5.1.2. It is set up so you need to login ie not guest checkout and on entering a coupon it validates okay and shows the discount check mark but doesn't update the order totals. On a second click of the apply button the page refreshes and the orders totals are updated as expected. I'm thinking it is probably an issue with the javascript or when it is being loaded. Perhaps a conflict with other javascript that is in use. I also noticed if I hover over the apply button and look at the url...it usually shows https://www.website.ca/_ but on the first page load no URL is shown. To work correctly I think it just needs a page refresh but I'm wondering if anyone else has experienced this or if it is unique to my install. Dan

The only other downside I can think of is the possible impact it might have on your search engine rankings. It could result in lower/shared rankings or even penalties I really don't know. When the browsers started throwing up warnings on all none HTTPS pages, most e-commerce folks just jumped on board --- taking the easier, softer way. Everyone already had SSL certificates so why not. Good luck in whatever you decide to do. Dan

Using HTTP is always going to be a security issue which is why the change was suggested. If you don't wish to do that, it's on you. Dan

I guess the short answer is...its a security issue. Dan

I wouldn't recommend that...these days browsers just warn about it and frighten customers away........can users actually turn off https? and if so, why would you want too? Dan

It is usually recommended that you change the first line in your configure.php file to https:// as well so it's like this...have you tried that? define('HTTP_SERVER', 'https://www.yoursite.com'); define('HTTPS_SERVER', 'https://www.yoursite.com'); define('ENABLE_SSL', true); Dan