Jump to content
Latest News: (loading..)


Popular Content

Showing content with the highest reputation since 03/18/2019 in Posts

  1. 3 points

    php 7.2 - updating CE

    I'm slowly but surely, as and when I can give time, updating the software. Thanks to all who are helping the software to move forward 👍
  2. 2 points
    A couple of bugfixes coming later on tonight. As well as one extra bonus (which was being tested but the shopowner testing it went dark on me), so I couldn't make it into a 28d release in time. This one removes the side columns on selected pages (eg to have less clutter on the checkout pages)... 28d is still available for those shopowners who would like to help out. Thanks.
  3. 2 points

    Email queuing system

    Whilst I have not seen what you are doing I have been following this thread with anticipation for anything better than is originally available. It sound like you are getting somewhere Gary. Well done. I would love to see a system where order status update emails could be written specifically for the update status replacing the standard 'your order has been upgraded to' emails. And the same with the 'new customer' or other emails. They are all a bit plain and do nothing for future sales. Like I say, cant wait to see where this leads as it sounds good.
  4. 2 points

    Email queuing system

    Code has gone out to two testers. Depending on feedback given over the next week or two, should see this system into the wild. It's close...
  5. 2 points

    Email queuing system

    It sends to whoever the shopowner is targeting with the individual modules. In the example modules I've come up with, that's all customers... I am certain this system is the acorn that will grow into what CE will use for emails in the future.
  6. 2 points

    php 7.2 - updating CE

    As PHP 7.2 is now fairly well established (and PHP 7.3 is starting to show up), any thoughts on how "Frozen" could be upgraded to work on 7.2 and up? If there are a lot of changes to make, perhaps general guidelines would be in order, rather than an exhaustive list of fixes (or even an add-on!). This would still leave a lot of work to be done by shop owners, but it may be the best we can do. Add-ons will be yet another issue. I presume that Edge is/will be PHP-7.2 ready out of the box, but there are still a lot of people on Frozen just because it's nice and stable. That's the one that I install for clients. Once Slushee comes out (next freeze of Edge), that is at least PHP-7.2 ready, I would assume that any further work on Frozen would cease. And oh, how about calling the next one osC 2.3.5? It's obvious that HPDL is never going to accept any of Gary's work as the official product, and he's probably never going to release another osC, so why not ease the confusion?
  7. 2 points
    JcM Product info description_tabs Select Have been updated to version 1.3 to make them multilingual. I am not going to update any other version of this so if you need multilingual then turn off curent version and uninstall module and the deleat files. Then simply copy over new files , install in admin and setup. For those who are using these but have mofified the code! well it's up to you to compare the changes and update if needed.
  8. 2 points
    lso I think you are a bit confused! osC is not magic! it will not auto create language files 😊 Yes the tabs at the moment are single language only as I made them for my site but all stock data used is stock osC and it's up to you to add the alternative text. This is you english page showing Swedish stock text This is your Swedish page again showing Sweedish stock text. Ig noring the tabs ( thats all down to me ) I can only assume yo have not added english text in you products in admin? To use osC as muliligual you have to add text in admin for every language you use. Also every time you change a product info you must make that change to all languages. which is a real pain in the butt! Hence I recommend using the Google Translate add-on. https://apps.oscommerce.com/mYuUD&info-box-with-google-translate-bs4
  9. 2 points
    Not posiable with current tabs. It's on a long list of thngs to do. You will have noticed I have been updating the ones people have asked for so this will join that list and when I have time it will be updated. Or you can do it your self, its not hard it's simple case of adding a language file and moving the defines from the class to the language file. This will mean that you then have to edit a language file in order make changes rather than simplely in the admin module edit. This should only be affecting new content such as tab names and such. All stock content is still mulitlingual! Or you can support the CE software and buy Burt's 28days as I belive it has tabs in it.
  10. 2 points

    Bootstrap 4 in

    Bootstrap 3 will be around for years - no point overthinking that, so forget it. The main "problem" will be upgrade php. Some people say php7.2 is working fine, others report it is not working fine. At the end of the 28d, dependant on support thereof, I hope to have gotten enough time in hand to get the following done and complete; make sure shop and admin are ready for 7.2 (at the very least, possibly 7.3 if I can swing it) -> no warnings and no errors product class -> rework relevant modules to use it But as with all things, one step at a time, and right now that step is trying to get some time in hand to actually do "stuff".
  11. 1 point

    A Question About Internal LInks?

    😊 The honist answer is I'm not sure as I don't fully understand how you are doing your links? PM me a link and I can try and see waht is happening. But in general the code goes into which ever page you wish the link to appear! you can see it in this test page I made. https://chilleddisplays.co.uk/modal_test.html As you see its just a text link that drives the pop up modal. when you click you get full screen modal for the shop. Try it and see if it's what you need. If not just the first simple link to new tab will do. Depending on what you first site is using ( PHP, HTML , js) you may need to mod the code a bit.
  12. 1 point
    Yes, this would only be valid for the version the original post relates to. It's a real shame the CE version is not the official release as any potential new users will use an alternative platform if they download the official release and get bugs.
  13. 1 point

    Article Manager v1.0

    To those that interested, there is a planned update, probably within the next few weeks.
  14. 1 point
    try this file. cm_header_nbrmenu.php
  15. 1 point

    28d 2019, let's move the Project forward...

    Problem was exactly as per the core code, just needed the addition of a clearfix div.
  16. 1 point

    Email queuing system

    Yes - the system does not yet replace the usual outgoing emails - but I am certain, in the near future, something like this system has to be put in place for all emails. Template-able Emails - it has to be the future!
  17. 1 point

    show 200 on product listing site

    @JariVSee the All Products SEO addon.
  18. 1 point

    Article Manager v1.0

    The last released version still uses defined names so it won't work in the CE versions.
  19. 1 point

    Email queuing system

    PWA uses an additional column in the customers table to flagg guest accounts (the ones which didn't have been auto deleted because the customer didn't finish correct on checkout_success.php). So to avoid sending e-mails to guest customers, shopowners can just add to the queries the condition: AND c.customers_guest != '1' or this could be used generic for all shops: AND (EXISTS (SELECT c.customers_guest FROM customers c) AND c.customers_guest != '1') I didn't check the code, but it should do it.
  20. 1 point

    php 7.2 - updating CE

    I've a little bit of time in hand and it seems like this is the next necessary thing to solve, the use of php7.2. But I need your help to point out any problematic area so that attention can be given to them. To help...you'll need an installation of CE (any flavour that is Frozen or later) running on php 7.2 - with error reporting dialled right up. To set up error_reporting to show everything that is wrong: includes/application_top.php Find: error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT); Change to: ini_set('display_errors', 1); ini_set('display_startup_errors', 1); error_reporting(E_ALL); admin/includes/application_top.php Find: error_reporting(E_ALL & ~E_NOTICE); if (defined('E_DEPRECATED')) { error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED); } Change to: ini_set('display_errors', 1); ini_set('display_startup_errors', 1); error_reporting(E_ALL); Save both files. Obviously...you DO NOT want to do this on a live shop as it will show errors to your customers, so hopefully a few people have a test shop to play with... Now if you browse your test shop...all warning and errors will appear. Thank you in advance. Please copy/paste the following as a reply: URL: WARNING/ERROR:
  21. 1 point

    Email queuing system

    Just ran a test order
  22. 1 point
    Please read the reply is gave!
  23. 1 point

    osC CE BS4 running on PHP 7.3

    So running for a few hours now and doing some basic testing and browsing on the site it's stable and working fine, also apperes to run a smoother than before! I know this is very subjective but it defnitly feels a little quicker. Checking the bench mark numbers reported PHP 7.3 is supposed to give about 10% overall improvment over PHP 7.2
  24. 1 point
    There is no need to worry about any state where you do not have a nexus (i.e., stay under the old rules). Just ignore other states, as they have no mechanism to enforce tax collection. Once they have implemented a streamlined system as I outlined in my previous post (and restated below), it will be painless to comply and I will be happy to do so. Until then, trying to comply with 45 or so states' sales tax rules is absurd and I won't do it. Write to your congresscritters (both representative and senators) and urge such a system to be adopted: A unified nationwide set of tax classes, so merchants only have to figure out what class a product or service falls under, once. Lookup tables published by states, organized by state and ZIP Code, with a single rate for each tax class. Leave it to each state to break down remittances into state, county, city, special district, etc. amounts. These should be CSV format that can easily be read into a database. Central clearinghouses must be authorized to distribute these tax tables so merchants have a central point to get their information and be notified of updates. A single point of remittance for any given merchant: one form, one CSV list of collected taxes per state/ZIP/class, one payment authorization. This might be a federal agency, several private agencies, or each state's tax agency. Remittance frequency would be annually for small firms up to weekly for the very largest businesses. There will be no exemptions for any business, no matter its size -- the idea is to make it so painless and simple that no one will be burdened, and reporting can be fully automated.
  25. 1 point
    24 posts in 11 years. You are part of the problem. If everyone gave a little bit of time and effort, the whole environment and ethos would be awesome. As it is we have people who popup every 4 or 5 years asking for help and advice, and giving back nothing to the community. That's something we need to (somehow) solve...