Jump to content

ArtcoInc

Members
  • Content count

    1,838
  • Joined

  • Last visited

  • Days Won

    31

Reputation Activity

  1. Like
    ArtcoInc reacted to burt in Optional Related Products, Version 4.0   
    Kneejerk comments that get edited.  Remember that some of us get to read it all  
    Would suggest that if one gets angered by someone elses comment...go and have
     beer/coffee/tea and come back with a clear head ready for posting constructively.
  2. Like
    ArtcoInc got a reaction from JcMagpie in Cart not charging tax. How to fix?   
    (when someone solves your problem, or answers your question, it's polite to 'Like' their answer)
  3. Like
    ArtcoInc got a reaction from JcMagpie in Cart not charging tax. How to fix?   
    (when someone solves your problem, or answers your question, it's polite to 'Like' their answer)
  4. Like
    ArtcoInc reacted to burt in Bootstrap 4 in 2.3.4.1   
    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".
  5. Thanks
    ArtcoInc got a reaction from René H4 in Bootstrap 4 in 2.3.4.1   
    @René H4
    If you search through the forum, you will find a lot of threads pertaining to PHP v7.2 support. PHP v7.2 is *much* more strict that prior versions, and many people are seeing warnings flag up all over the place. Do note that these are warnings, and not errors.
    AFAIK, 'Frozen' is not 100% compatible with PHP v7.2, and many (if not most) of the add-ons out there are also not 100% compatible. 'Edge' *may* be, but since 'Edge' is constantly changing, it may not be the best choice for a live shop.
    If you wish to deploy 'Frozen', I would suggest that you either roll back to PHP v7.1, or prepare to address any warnings or errors that arise using PHP v7.2. If the latter, you could also contribute back to the community with a list of the errors you find, and your solutions to them.
    HTH
    M
  6. Thanks
    ArtcoInc got a reaction from René H4 in Bootstrap 4 in 2.3.4.1   
    @René H4
    If you search through the forum, you will find a lot of threads pertaining to PHP v7.2 support. PHP v7.2 is *much* more strict that prior versions, and many people are seeing warnings flag up all over the place. Do note that these are warnings, and not errors.
    AFAIK, 'Frozen' is not 100% compatible with PHP v7.2, and many (if not most) of the add-ons out there are also not 100% compatible. 'Edge' *may* be, but since 'Edge' is constantly changing, it may not be the best choice for a live shop.
    If you wish to deploy 'Frozen', I would suggest that you either roll back to PHP v7.1, or prepare to address any warnings or errors that arise using PHP v7.2. If the latter, you could also contribute back to the community with a list of the errors you find, and your solutions to them.
    HTH
    M
  7. Like
    ArtcoInc got a reaction from ce7 in Product Name length   
    @ce7
    This is all I know ....
    You may need to contact @burt directly for more info.
    M
  8. Thanks
    ArtcoInc got a reaction from ce7 in Product Name length   
    @ce7
    Also, read this thread:
     
    There is also information in this thread ... I needed to fix an 'equal-height' issue, and two add-ons were suggested. One worked for me.
    HTH
    M
  9. Like
    ArtcoInc got a reaction from ce7 in Product Name length   
    @Hotclutch
    IIRC, @burt removed the equal height module in Frozen, having replaced it with a CSS solution.
    M
  10. Like
    ArtcoInc reacted to MrPhil in Admin-Configuration-My store How to add zones? FROZEN: osCommerce Online Merchant v2.3.4.1 CE   
    null is a special keyword with a special meaning. It does not get quotes around it, nor is it capitalized.
    Some older versions of MySQL may have allowed '' instead of null.
  11. Like
    ArtcoInc got a reaction from fantomen in Admin-Configuration-My store How to add zones? FROZEN: osCommerce Online Merchant v2.3.4.1 CE   
    @fantomen
    You don't want to change the database fields, you want to change the value of the data you are inserting into the fields.
    I think what @MrPhil was suggesting is this:
    INSERT INTO zones (zone_id, zone_country_id, zone_code, zone_name) VALUES ('null',203,'AB','Stockholm')
    1) Back up, back up, back up!
    2) I do not know if the 'null' data needs to be surrounded by single quotes or not. Probably not. You may have to try either or both.
    3) You will have to make this change to all of the records you are inserting into the database.
    HTH
    M
  12. Like
    ArtcoInc reacted to burt in Removing "welcome to my Shop" in index   
    Is the correct answer and has been since prior to release of "Frozen".
     
  13. Like
    ArtcoInc got a reaction from burt in Removing "welcome to my Shop" in index   
    @honda4
    Admin -> Modules -> Content -> Page Heading (shown under 'Index') -> edit
    Set enable to false
    HTH
    M
  14. Like
    ArtcoInc reacted to burt in BS Bundled products at a discount addon required   
    May drop it into the upcoming 28d...debating whether to do so.
  15. Thanks
    ArtcoInc got a reaction from Kurre in Credit Class and Gift Voucher 5.14   
    @Kurre
    This might help ...
    M
  16. Like
    ArtcoInc got a reaction from puggybelle in Hack attempt - is there a way to prevent this?   
    @puggybelle
    (while off topic ...)
    As I said, the Community Edition does not have an accurate version numbering system.
    When Burt started this project back in 2014, osC was at version 2.3.3.4. So, the Community Edition, all through its early development, was also v2.3.3.4. Every release during these early times was called v2.3.3.4.
    When osC upgraded to v2.3.4, Burt brought the Community Edition code base up to the v2.3.4 code base, and the Community Edition stayed at v2.3.4 while further development was happening. Somewhere during this time, Burt released the 'Gold' fixed release. Development still continued, with every release still being called v2.3.4.
    When osC had the v2.3.4.1 Hot Patch applied, Burt also applied the Hot Patch, and the Community Edition was bumped up to v2.3.4.1. Once again, development continued, with every new release still being called v2.3.4.1.
    Burt released the 'Frozen' fixed release in August, 2018. Development still continues (usually called 'Edge', although that is not a fixed release), and the version number is *still* v2.3.4.1.
    Some bugs have been identified in 'Frozen', and there is a thread here on the forum identifying them (and some fixes too). 'Edge' continues to be developed (still being called v2.3.4.1), and some significant changes have been made since 'Frozen', causing some compatibility issues with prior versions, and many (most?) add-ons out there.
    This all said ...
    You can download the 'Frozen' version (see the link in my signature below). *** IF *** you have made NO core changes, you *should* be able to drop the 'Frozen' version into your store. Otherwise, you will need to use a file compare application to see what changes have been made since your release.
    (now, to get back on topic ...)
    How this all relates to your initial problem, I don't know. Someone with a higher pay grade than myself will need to explore how the injection code made its way into your orders record.
    M
  17. Like
    ArtcoInc reacted to Jack_mcs in Hack attempt - is there a way to prevent this?   
    When the form is submitted, the commands are stripped from it. That is why you see the __script instead of <script. That renders the code useless as far as the hacker is concerned. At least it should. I never assume anything when they are involved.
    If you have an addon that records the IP, like View Counter or IP Blocker, then you should block the IP. That won't prevent others from using the same method but it might stop that guy.
  18. Like
    ArtcoInc reacted to raiwa in Hack attempt - is there a way to prevent this?   
    PWA uses exact the same coding which sanitizes customer input to store the customers data in the database like the core create account page. So it is as save as the  core create account in that sense.
  19. Like
    ArtcoInc got a reaction from valquiria23 in How to distinguish the sub categories in the category box?   
    @MyBookShop
    Do you have this installed on a live site? If so, can you post (or pm) your site URL?
    M
  20. Like
    ArtcoInc reacted to MrPhil in Additional Protection With htaccess/htpasswd secured through htaccess/htpasswd means.   
    Eh? You're talking about the same thing!
    Anyway, there are up to four layers of protection to keep bad guys out of your shop administration:
    Using SSL so they can't "snoop" on the admin traffic. The whole site should be under SSL (https) these days, so that's a moot point. Administrator ID and password -- not easily guessable, right? Unguessable admin directory name. The first thing every hacker tries is to get into your <domain>/admin area, so changing admin to something weird is good. Server "password protection" on admin and everything under it. This means having to "log in" a second time to get in. Of course, the ID and password you use is different from the Administrator ID and password, right? Number 4 is the issue at hand. You are much better off using your control panel's "password protect a directory" function than trying to install the files supplied with osCommerce. The former is guaranteed to work and is easy to install, while the latter is iffy and difficult to install. The only downside to using your control panel function is that osC's security check may not recognize that you did it, and report that there is no password protection, when there is. If you have to give two separate logins to get to your admin functions, it's working.
    Many sites choose not to do #4. It's less secure, but that's up to your comfort level.
  21. Like
    ArtcoInc reacted to raiwa in Purchase without account for 2.3.4 and BS2334   
    Hello Anne @Dj-Viper,
    I'm going back to the public forum. Others may have a similar problem and can profit by the information.
    Most payment modules use the standard checkout processing through checkout_process-php. Orders are created, stored and the order confirmation mails created in that file.
    But some payment modules bypass this file and do their own order processing including the order confirmation mail creation in the payment module. The coding is therefore included in the payment module.
    The only payment module included in a standard oscommerce store doing so is PayPal standard.
    Now in your case the "payment processor ideal" you are using does the same. You have to apply the modifications in this payment module which is located in: includes/modules/payment/.
    Please use the instructions for the PayPal standard module as a guide how to apply the PWA modifications to your payment module. Instructions may not fit literally the code of your payment module, you have to try to find the equivalent code.
    Also add your modifications to include the customer mail and phone there.
    You do not need to apply the modifications to all payment modules, only the ones which bypass the standard checkout_process.php like your "payment processor ideal" and therefore do not use the modifications done in checkout_process.php.
    Hope this clears up your questions and helps
    Best regards
    Rainer
  22. Thanks
    ArtcoInc reacted to BrockleyJohn in PHP 7   
    @ArtcoInc generally speaking, it shouldn't be a problem. There is syntax on 7-7.2 that isn't supported on 5.6 but you're probably not going to be using any of it in your new version... spaceships <=>, null coalescing ($action = $_GET['action'] ?? 'default'), anonymous classes, constant arrays and a bunch of other things that don't spring straight to mind.
    The only bit of code I can think of that doesn't work across versions is something to do with error-handling on evals but you probably haven't got any of that anyway. The evaluation order in statements is the other way round (eg. when working out what $$class->$method($param[$$key]) means but that should have been fixed by putting in curly braces to make it expllicit in the statement.
    The approach would be - get a set of code running without issue on 7 and then turn the version back down to 5.6 for a test.
    hth
  23. Like
    ArtcoInc reacted to MrPhil in Who in the EU has heard of GDPR and will it affect you   
    Seen on the 'net. Sing along!
    He's making a list,
    He's checking it twice,
    He's gonna find out who's naughty or nice,
    Santa Claus is -- in contravention of article 4 of the General Data Protection Regulation (EU) 2016/679.
  24. Like
    ArtcoInc reacted to stratula in Entscheidungsfindung   
    @Chrisso
    here is a good working german language pack
    German language pack for BS_CE
  25. Haha
    ArtcoInc got a reaction from 14steve14 in Bootstrap 4 in 2.3.4.1   
    The domain BuyBurtABeer.com is available
×