Jump to content
Latest News: (loading..)

ArtcoInc

Members
  • Content count

    1,523
  • Joined

  • Last visited

  • Days Won

    30

Reputation Activity

  1. Like
    ArtcoInc got a reaction from burt in Return to Top App   
    @burt Didn't you make a 'Return to Top' module for one of your 28 days bundles?
    M
  2. Like
    ArtcoInc reacted to burt in 28d 2019, let's move the Project forward...   
    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. Like
    ArtcoInc reacted to René H4 in 28d 2019, let's move the Project forward...   
    Now the period of 28d has ended, and all smaller and larger programs have finished, I can highly recommend these products and purchase them from Gary.
    Not only have I installed around 20 modules ( and added my own child modules that were ideas born from one of the 28d), but also Gary has been very supportive all over the 28 days.
    So when in doubt, and if you need to see one of his modules in a commercial shop, do not hesitate to contact me and I will direct you to my shop.
    Again, well done Gary!
    René from the Netherlands.
  4. Like
    ArtcoInc reacted to burt in 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.
  5. Like
    ArtcoInc reacted to burt in 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...
  6. Like
    ArtcoInc reacted to burt in 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 👍
  7. Like
  8. Like
    ArtcoInc reacted to burt in Frozen bug list   
    https://github.com/gburton/Responsive-osCommerce/commit/59be0a7e877698564f4c2a3c6aea6faab700050d
  9. Like
    ArtcoInc reacted to burt in Frozen bug list   
    https://github.com/gburton/Responsive-osCommerce/commit/9c86f9bd90c6b1fcbaa92777a0e3cfcf1f6fcc09?diff=split
  10. Like
    ArtcoInc reacted to burt in Frozen bug list   
    https://github.com/gburton/Responsive-osCommerce/commit/8147bed4a2f606964504772337f6da8ae43c853e#diff-13dae7d4d9c5a71489a5d3523e16b1b5
  11. Like
    ArtcoInc reacted to burt in Frozen bug list   
    https://github.com/gburton/Responsive-osCommerce/commit/1b472838b10726395d8a2cad72192b64ebcc6065
  12. Like
    ArtcoInc reacted to burt in Frozen bug list   
    https://github.com/gburton/Responsive-osCommerce/commit/6a22a99c32df450fa982814d0fa07aa6102d4f76?diff=split
  13. Like
    ArtcoInc reacted to burt in Email queuing system   
    Adding in those extra {{XYZ}} tags has caused problems.  Main problem being on the admin side when adding an email into the Queue, the extra {{XYZ}} tags over and above the basic (always available) ones were impossible to add. 
    That's now solved after much banging of head on keyboard.  So, I think it's now good to start being properly tested - over the weekend I'll upload the new files to the demo site, clean out the queued emails and ask for testers (once again, sorry)...
  14. Like
    ArtcoInc reacted to burt in Email queuing system   
    Another full day of coding this, the joys of being a coder.  I now have it as easy as possible to add in {{XYZ}} tags, and they automatically show in the admin side as available for use.  Eg on the "no_checkout" slug I added in {{SIGN_UP_DATE}} (which is the date customer created account) and in the admin side it appears like so ready for use;

    It's not as simple as I'd like, but I think I've done as much as I can working within the confines of the osCommerce architecture...
  15. Like
    ArtcoInc reacted to burt in Email queuing system   
    I haven't.  I'm aiming to get something useable for "out of the box" osC...and then if individuals need technical advice/changes, I'm available as usual.
    Long story short, for something like PWA (note that I do not know exactly how PWA works but have a general idea), it would just mean working out what data is available and creating a an outgoing-email module for that data.  To make a long story even shorter; not difficult I think.
    As for something like a winback (or any other outgoing-email module) that would be up to each shopowner to decide what is right for their demographic...as simple as that...
  16. Like
    ArtcoInc reacted to burt in Email queuing system   
    It'll go out to 28d people soon 👍
  17. Like
    ArtcoInc reacted to burt in Email queuing system   
    Great, it's looking good...

    Burty signed up today but didn't complete a checkout
    - Email will go out in 5 days asking if there was a problem ***
    - Email will go out 31 July with birthday wishes (21 days prior to his birthday) Dan signed up today and gave his birthday, and completed a checkout
    - Email will go out 27 April wishing him a happy birthday (approx 3 weeks prior to birthday)
    - Email will go out 10th May (60 days) asking for a review
    - Email will go out 10th March 2020 asking why he hasn't ordered for a year *** Rene completed a checkout today
    - Email will go out 10th May (60 days) asking for a review
    - Email will go out 10th March 2020 asking why he hasn't ordered for a year *** Steve completed a checkout today
    - Email will go out 10th May (60 days) asking for a review
    - Email will go out 10th March 2020 asking why he hasn't ordered for a year *** *** - these emails get cancelled depending on customer interaction. 
    As an example, let us say that Burty logs in 2 days from now (13 March)...and completes a checkout...what happens:
    no_checkout is cancelled as he has now checked out request_review goes out in 60 days (so May 12th or so) from the date of sale winback will go out about 13th March 2020 asking why he hasn't bought anything for a year (remembering that this would be cancelled if he did log in inside that year) Pretty cool little system ?  I'm pleased with how it's turned out.  You may have noticed I made a "no_checkout" slug - it took less than two minutes, no core code changes - all plugged into the system automatically.  BOOM!  That is the future of osCommerce.
  18. Like
    ArtcoInc reacted to burt in Email queuing system   
    These two (especially the reviews one) are game changing for shopowners, in my opinion. 
    I'm trying to make another game-changer based on the ideas in this thread and have gotten it sort of working;

    In this example, a new customer "Donald Duck" just signed up...he gave his birthday as 10th November 1960;
    send at (birthday) will go out 21 days prior:  20th October send at (shipping follow up) will go out in 21 days from now send at (request review) will go out 30 days from now That's the basis of this system.  I will also create an admin page where shopowner can easily see the email queue and delete/add emails.
    This is a complicated project, but I have it under control.
    Any more ideas for emails to go into the Email Queue?
  19. Haha
    ArtcoInc got a reaction from burt in 28d 2019, let's move the Project forward...   
    "Dem dat know, know that they know.
    And dem dat don't know, they don't know they don't know."
    M
  20. Like
    ArtcoInc reacted to cigarsforless in 28d 2019, let's move the Project forward...   
    28d is hard to find and lacks publicity I think.
    shame there is so little turnout as your work on osc is immeasurable
  21. Like
    ArtcoInc reacted to burt in 28d 2019, let's move the Project forward...   
    The idiot that coded these things...should have done a little more testing. 
    It's definitely shopowners who are the best testers...
    So, a few bugfixes have just been sent out - mostly very minor.
    In all cases, just upload the files included to replace the old.
    Thank You to all who pointed out my mis-steaks 👍
  22. Like
    ArtcoInc reacted to burt in Frozen bug list   
    https://github.com/gburton/Responsive-osCommerce/commit/4a322f66cc357316ee14ac67f4112f05c12d4c07#diff-d3af7f021910d88b81d38ef5f88163c8
  23. Like
    ArtcoInc reacted to burt in 28d 2019, let's move the Project forward...   
    28d21 - Bundled Products
    (sorry for early post, I am unavailable almost all day tomorrow)
    For d21 I have the third of four "bigger" mods.  This one allows you to sell a Bundle of Products.
    Admin Side 
    New Page for creating Bundles
      Shop Side
    module that display the Bundle
    module that reduces stock appropriately Core Code Changes:
    NONE.  System is 100% modular.   Upload, turn on, create Bundle(s).
    Demo:
    https://template.me.uk/28d2019/product_info.php?products_id=29
    This is the "Stephen Seagal" bundle - where all products are available in required quantities...


    https://template.me.uk/28d2019/product_info.php?products_id=30
    This is a "test" bundle where one of the product does not have sufficient stock

    Admin Hook
    Also included is a Admin Side HOOK - which means you do need to have the Hooked Order page installed - comes as standard in Responsive...
    This Hook shows shopowner a quick reminder of Bundled Content for easy stock-picking.

    Delivery:
    As noted earlier, I am out most of the day tomorrow, so this one will come to you late tomorrow night (or poss friday morning if I do not get back in time).
  24. Like
    ArtcoInc got a reaction from fantomen in Regarding the contribution: Edit pages via Admin   
    @fantomen
    I understand the convenence of being able to edit information pages through Admin, and not having to deal with uploading new files anytime you want to change the text in these pages. In fact, I have used one of these type of packages in one of my shops. However, I won't be using one for any future shops, and I will most likely remove it from the existing site. Here's why:
    I find that for the type of shops I run, I want the information of ALL pages to be searchable. If a customer enters a search request for some information that is on one of these pages, they won't find that page using one of these packages. So instead, I am using a search module that allows my customers to search products, categories (where I have a LOT of information), and any standalone page that uses a language file to display that page's content. So, if my customer searches for "entertaining" or "adult only", they can find those expressions, even if they are not in a product's name (the stock search function is limited to just the product name).
    Also, pay attention to how these packages work if you intend to have more than one language on your shop.
    HTH
    Malcolm
  25. Like
    ArtcoInc got a reaction from fantomen in Regarding the contribution: Edit pages via Admin   
    @fantomen
    As @Jack_mcs has pointed out, this add-on was written for an earlier version of osCommerce. You can adapt it to 'Frozen', but it will require a few edits to the add-on code. While I have not downloaded this add-on to examine the code, here are some of the changes you will have to make:
    Some time ago, Burt got rid of the filenames.php and database_tables.php files. Instead, all calls to a file, directory, or database table are now hard-coded (in both the core code, and in any add-on). You can address this in one of two ways:
    1) Install the compatibility add-on
    http://addons.oscommerce.com/info/9506
     
    2) Hard-code the paths into this add-on. This is not difficult to do ... probably the biggest mistake people make is that they miss one (or more) of these needed edits.
    (like I said, I have not downloaded this add-on, so the following example are just that ... examples. You will have to find the applicable code in your add-on)
    Search through the code, and wherever you find something like this:
    require(DIR_WS_LANGUAGES . $language . '/' . FILENAME_CREATE_ACCOUNT); notice the names in capitol letters. You will have to change both of these:
    a ) Where it says DIR_WS_LANGUAGES , this was a definition in the configuration file telling where the LANGUAGES directory is. You will need to change this to the actual directory name, which in this case is languages/.
    b ) Where it says FILENAME_CREATE_ACCOUNT, this is where the filenames.php file defines what the CREATE_ACCOUNT file is called. You will need to change this to the actual file name, which in this case, is create_account.php.
    Changing both of these will result is something like this:
    require('languages/' . $language . '/create_account.php'); (like I said, this is just an example, and not some actual code from this add-on)
    So, just go through all of the code in the add-on, and search for anything with all capitol letters. If it starts with DIR_ , it is a directory name. If it starts with FILENAME_ , it is a file name.
    c ) In any database call, you will see something like this:
    $query = tep_db_query("select a.customers_id, a.customers_firstname, a.customers_lastname, b.entry_company, b.entry_city, c.zone_code from " . TABLE_CUSTOMERS . " AS a, " . TABLE_ADDRESS_BOOK . " AS b LEFT JOIN " . TABLE_ZONES . " as c ON (b.entry_zone_id = c.zone_id) WHERE a.customers_default_address_id = b.address_book_id ORDER BY entry_company,customers_lastname"); let me reformat that to be easier to read ...
    $query = tep_db_query("select a.customers_id, a.customers_firstname, a.customers_lastname, b.entry_company, b.entry_city, c.zone_code from " . TABLE_CUSTOMERS . " AS a, " . TABLE_ADDRESS_BOOK . " AS b LEFT JOIN " . TABLE_ZONES . " AS c ON (b.entry_zone_id = c.zone_id) WHERE a.customers_default_address_id = b.address_book_id ORDER BY entry_company, customers_lastname"); There are three entries that begin with TABLE_ . These are the database table names, and will now have to be hard coded. In this case, TABLE_CUSTOMERS refers to the customers table, TABLE_ADDRESS_BOOK refers to the address_book table, and TABLE_ZONES refers to the zones table. So, the edited command would now be:
    $query = tep_db_query("select a.customers_id, a.customers_firstname, a.customers_lastname, b.entry_company, b.entry_city, c.zone_code from customers AS a, address_book AS b LEFT JOIN zones AS c ON (b.entry_zone_id = c.zone_id) WHERE a.customers_default_address_id = b.address_book_id ORDER BY entry_company, customers_lastname"); (like I said, this is just an example, and not some actual code from this add-on)
     
    d ) One other coding style has changed, preparing osCommerce for newer versions of PHP. In the code, you may find something like this:
     
    $email_address = tep_db_prepare_input($HTTP_GET_VARS['email_address']); if (!@ $HTTP_POST_VARS['action']) { Whenever you see a $HTTP_POST_VARS or a $HTTP_GET_VARS, these will need to be changed to $_POST or $_GET, respectively. Please note that these changes are to make the code compatible with newer versions of PHP, and is not an indication of the add-on, or of osCommerce.
    If you can apply all of these changes, and get this add-on to work properly, you could then give back to the community by uploading your updated code to the add-on repository.
    If you find that this it too much for you to do, you can always post in the commercial portion of the forum to hire someone to do this for you. If you do do this, please pay it forward by uploading the revised code to the repository.
    Or, as @Jack_mcs has suggested, you could try another add-on.
    HTH
    M
     
×