bcsteeve

Hey, that's great! And it only took 7 years and 2 months to solve this issue. I'm not detracting from your efforts. I'm pointing out [one of] the reasons people should run for the hills when considering this web application for use with their business, where they may need faster response times than the average life of a [spam-filter].

I moved on a long time ago now. I really liked how PrestaShop looked and felt... but it is so absolutely broken with such poor official and community support that it really wasn't worth it any more. At every single turn, it is all about someone trying to sell some overpriced add-on/fix. That's not a good model. PrestaShop is one of the most promising and well thought-out platforms I researched (and I researched a LOT)... but it is only skin deep. Its like they got so far and just gave up. Too bad, really.

Almost. Try this: Find a shopping cart software that makes sense and works instead of just looking pretty. Switch to that shopping cart software. Take note on their forum if it takes weeks or months to get support, or if the only answers you see are people telling you to to go a different cart.

I didn't know that. Is there a downside?

I actually can't think of a reason to refute that... except that was never the recommended practice. Most sites only use SSL for sensitive pages. There has to be a reason for that, no? Performance?

I needed help when I posted. Help never came. A sales call came 3 days later, followed by a nonsense argument, but help never did arrive. Its OK. I moved on like everyone else.

When you install Windows, you can go into your settings and choose from several INCLUDED background images. It is a decision you make. It is INCLUDED. This is no different. Why you get so stuck up on semantics rather than seeing things the way they are, I'm not sure. Oh right, its because of your financial vested interest and your subtle desire to have people uninstall the included modules so you can sell your paid ones.

"actually" no, not until you offer up your modules for free. The whole model of P(o)S is to give the user broken software that needs to be fixed with paid 3rd party modules. Of course as long as you're profiting from the model (and so are they) you'd espouse the "its free, so ignore its flaws" mantra. Makes it no less BS.

Absolute doesn't work. That's only a good suggestion for those not using https (which means they aren't an ecommerce shop) or they're only using https (which I rarely see done so there must be a reason not to?). Or are you saying the site should be https only? So the customer types in www.example.com and a redirect takes them to https://www.example.com and they stay there the whole time? Or I'm missing something because when I tried absolute, I got security warnings on my https pages.

Nope, not free... opensource (we've been around this block already)

I know that is your take on it, but it is the one that was installed with 1.6.10. How PrestaShop chooses to distance itself from its modules is its business. I downloaded Prestashop and it comes with modules, some installed, some not. But it is included. USA/Canada, in any event. And the "way it works" vs "broken like a sick monkey" are two entirely different concepts.

Maybe. Hmm. So you're telling me that if your domain is www.example.com and your site is in a folder called "shop" (and so your base uri is defined as www.example.com/shop) and you're editing a product description and you want to put in some photo that's located at http://www.example.com/shop/img/myphoto.jpg that you would hit the source button and type in something like this: <img src="/img/myphoto.jpg"> and when you save it, go back in and click source again you still see above and not: <img src="http://www.example.com/shop/img/myphoto.jpg"> or <img src="../img/myphoto.jpg"> ??? If that's the case, then yes perhaps something is up on my end. I did follow someone's advice here to "extend" tinymce in order to fix some other problem I was having early on that I can't even remember now. Please confirm above and then I'll do some digging. Perhaps I'll start over (again) with a fresh copy.

If you haven't edited your .js specifically, then you're wrong on that. Editing with the source code button changes nothing. It re-writes, by default, what you enter upon save regardless of what mode you were in when you entered it. It cleans the HTML, strips away a lot of things... and "corrects" your URLs. If you have edited your .js config script to disallow url rewriting then that's different (but something you should mention when giving such advice). Again, I've seen several posts warning against doing that.

The PayPal one that is included with a fresh install of 1.6.10.

umm... as I wrote above. What do you mean, how do they look? You just concluded with the opposite of your preceding instruction. Starting with / doesn't work. That's what I was doing until I saw tinymce rewriting the url to either ../ or absolute as per setting. I can turn rewriting off, but that is advised against in several forum posts, and frankly if that is necessary then this should be considered a bug.