Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by burt

  1. Lots of things get removed/changed in order to facilitate the forward movement of the codebase. Filenames and DB tables - easier installation of addons/apps Cache - antique system. Actually slowed down Phoenix in testing. The beauty of the open code base is such that anyone can add it back in to suit their needs.
  2. burt

    Paypal Standard Payments Failing

    @Cary @Mac Fly
  3. Please also (as @Mac Fly has done) raise a support ticket with Paypal. Let's see what they have to say (to both)...
  4. That is a two-way street. As you say, never mind.
  5. You have asked that question via PM and you got your answer via PM. Yet here you are, stirring the pot of negativity. <--- that is why
  6. Says the guy who got chucked out of the Phoenix club for an attack on another member. LOL.
  7. Yeah, there's a few in this forum who would prefer to see osCommerce dead rather than have me as the one pushing it forward.
  8. Fake News. It stops today. Take this as a friendly reminder to be positive instead of constantly negative.
  9. user.css https://github.com/gburton/CE-Phoenix/blob/master/user.css This would be located in the root of your Phoenix installation.
  10. burt

    attribute prices

    On a backburner.
  11. burt

    attribute prices

    This is something that is still on the to-do list. It was arranged with a developer for this backport (along with modern updates) to be done and put into Phoenix Core but "things didn't work out" so although it was at an advanced stage, it had to be put on the backburner. I'm still hopeful we can somehow revive [Henry was going to do it and not sure if he is still available/interested] it but it's a long way off I think due, as always, to budget.
  12. burt

    Phoenix Dashboard

    Malcolm artcoinc and I posted pretty much the same thing at the same time. All code is on github, fill your boots. We've got some really nice things in the pipeline.
  13. burt

    Email queuing system

    It did get finished but it turned out to be one of the projects where things didn't quite go according to plan, and the code ended up not being ready for public release. I do plan to revisit it soon as part of the Phoenix Updating process as this system (or something similar) would supercharge outgoing (and incoming) customer contact.
  14. @TomB01 Exactly this. This is the main reason why I output updates in bite-size chunks on a fairly regular basis. It allows those who want to keep up-to-date the ability to do it in an easy 5 or 10 minutes. It also allows those who can't or don't want to take that time to come back to it at a later date or even to disregard the point updates entirely and just do an update blowout on each .0 release. Point being; take your time. If there was anything super important to get done "NOW" (eg if a insecure thing appeared or some show-stopping bug was introduced between versions) I'd be sure to mention that in the relevant version update post to try to get shopowners to get that part of an update done pronto.
  15. I usually just do everything bar the configuration and configuration_group tables (which are the two "controlling" database tables). Then make sure that all the tables I just brought over have the same columns [and settings] as a core Phoenix.
  16. We (that is Henry and I) months back, had plans to update the DB schema to make things uniform across tables. customer_id, customers_id, customers_info_id => customer_id language_id, languages_id => language_id and so on. This would make the possibility of doing some super things with joining and filtering and reporting etc. But as with loads of other things, it's on a backburner as there are loads more important things in the list. Sorry that doesn't answer the Q, but is somewhat related. It's on the to do list.
  17. Phoenix All the other names you mention are older versions, no need for explanations. Current version is v1.0.4.2 [ here ]. I have not yet had chance to update the official downloads page [which shows v1.0.4.0].
  18. burt

    Product listing

    I cannot see the thread either. Some time back last year...a lot of threads went missing due to a cock-up. Can only assume this was one of those threads, caught up in that.
  19. @well-wazh Ne donnez jamais accès à votre site à quelqu'un que vous ne connaissez pas ou en qui vous n'avez pas absolument confiance. Never give out your access details to anyone you do not know or do not have absolute confidence in. http://www.oscommerce-fr.info/forum/ is the francophone osCommerce.
  20. The only reason for "security pro" was poorly coded addons. If you do not add poorly coded addons, then you should not need it. Hence my request that you show a q-string manipulation at the Demo site - the demo site has no addons. If you can't show an example, then I will amend the topic title to more accurately reflect the thread.
  21. Show an example of such at the Demo Site: http://template.me.uk/phoenix/ In other words post up a URL that includes the injection so that we can see the produced output. Then it is possible to further diagnose if that is what is needed.
  22. burt

    SMTP email not able to send out

    The "ownername" email address has to be an address of the domain on which your shop is at. This is a Hosting setting and your host is...clueless...not to tell you that.
  23. I keep getting offered it whenever I use Paypal. I keep saying "no thanks". It's a `buyer opt-in` thing I think, and once opted-in...it should just work.
  24. In the language file of the module No plans for this https://github.com/gburton/CE-Phoenix/releases should answer the question