Jump to content

altoid

♥Ambassador
  • Content count

    1,567
  • Joined

  • Last visited

  • Days Won

    13

Reputation Activity

  1. Like
    altoid got a reaction from Mikepo in Email queuing system   
    Agreed. Very spiffy.
  2. Like
    altoid got a reaction from Mikepo in Email queuing system   
    Agreed. Very spiffy.
  3. Like
    altoid reacted to burt in Email queuing system   
    Idiot I forgot one important part of the whole thing:  order_id
    Without that order_id as an available {{OID}}, shopowner cannot direct the customer to (eg account_history_info.php?order_id=X - which would obviously be very useful.  I don't have time today (out most of the day) but will get that into the system later on tonight ready for testing.
    And then I'll get the full system out to a couple of shopowners for real-life testing, and dependant on the result of that...out into the wild.
  4. Like
    altoid reacted to Mikepo in Email queuing system   
    I agree, great Addon
  5. Thanks
    altoid reacted to burt in Email queuing system   
    It'll go out to 28d people soon 👍
  6. Like
    altoid 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.
  7. Like
    altoid reacted to burt in Email queuing system   
    @René H4

    60 days (choosable by shopowner) from now send a review request
      365 days (choosable by shopowner) from now send a "haven't seen you for a year" winback email
    If in the meantime, you were to buy something (say in 6 months)...that winback would
    be deleted and a new one a year from the next sale would be put in its place.
  8. Like
    altoid reacted to burt in Email queuing system   
    I've installed this system on the 28d Demo - and, so far so good.  
    I (as admin) manually inserted an email in the Queue - set for a few days ago - so it would fire off immediately. 
    Here's the Slug:

    Here's the received Email:

    TL:DR;
    The whole system is working as intended! 
    I'll test it a bit more and then get a couple of shopowner to raise their hands for testing...
  9. Like
    altoid reacted to burt in Email queuing system   
    And here's the Slug page, aka email templates...

    So, just one more thing to do...send out emails at about the right time, and make sure the emails use the merge_vars as shown (anyone who runs Mandrill will understand merge_vars).  But in this relatively simple system, assuming an email was going out to Donald Duck, the word {{FNAME}} would be replaced with "Donald".
    So, next step is to tie it all together and see if the concept works...
  10. Like
    altoid 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?
  11. Like
    altoid reacted to raiwa in Purchase without account for 2.3.4 and BS2334   
    Update uploaded:
    Purchase without account BS 3.0.5.
    Changes Version. 3.0.5
    - fix in admin/reviews.php to show guest reviews flagged. Thanks to @Demitry
  12. Like
    altoid reacted to Jack_mcs in [CONTRIBUTION] Ultimate SEO URLs v2.1 - by Chemo   
    A new version has been uploaded. Itjust fixes the problem with the ConnectDB introduced in the last version. If you have applied the fix mentioned in this thread, you don't need the update. But if you want to apply it, just upload the includes/classes/seo.class.php file.
  13. Like
    altoid reacted to gummipingvin in Feedback for raiwa   
    First I bought a module from Rainer, excellent replies - fast service, and very good communication.

    Raiwa more than exceeded my expectations, after some problems with installation due to our heavily modded shop - which the module was not made for - he installed it for us, with very good documentation and testing.
    After this we asked for some modifications to the module, everything have been done very professional.

    Can't find anything to put a finger on - so can warmly recommend anyone to use him for any OsC work!
  14. Like
    altoid reacted to Jack_mcs in Fake accounts   
    If you are comfortable changing the code, find this in the includes/functions/honeypot.php file
    tep_db_query("insert into " . $db_table . " set " . $insert_sql_data); and add this above it
    if (MODULE_HEADER_TAGS_HONEYPOT_CREATE_ACCOUNT_NOTIFICATION == 'True') { HoneypotNotify($cust); } You can add // before the two lines farther above that read
    HoneypotNotify($cust); That will give you an email for all accounts that are created.
  15. Like
    altoid reacted to Jack_mcs in HoneyPot Captcha   
    A new version has been uploaded with these changes:
    Added option to block account creation based on thr number of accounts and/or time accounts added.                   Added back some of the url checking removed in the last update to catch stragglers. Removed the PWA code in the create account page for pre-2.3 shops since it did not apply to this addon. This version aims to prevent the account creation of many accounts by scripts. There are two ways it does that.
    First, you can set a count for how many accounts may be created. So if it is set to 2, each customer can only create 2 accounts. If your site has legitimate customers that need more accounts, then don't use this setting or set it higher.
    Second, the code records the IP of the account creator as well as the time the account was created. If another create account is attempted by that IP in the time entered in the settings, the account won't be created.
    Both of the above can be used together or alone.
  16. Like
    altoid reacted to JcMagpie in Fake accounts   
    I am afraid you are mistaken. Bots these days are very clever they are able to bypass simple attempts like you have made. They even now are able to get past the honeypot method. Do not underestimate how clever spammers are.
    You will need to use several layers of protection to reduce the spam levels.
    Begin with secure forms and I mean all forms on your website.
    1) Use honeypot and Google recapatch if you can.
    2) use .htaccess file to block if you can
    3) use your server (cPanel or other) IP blocker if you can
    4) Make sure you have a spam fillter set up on your email server.
    It's just a starting point as with spam you just have to keep updating as the spammers evolve.
    one of the worst spammers at the moment is,----- well i will not post the name but it's .ru  this is the ip range they use currently add it to your server IP block list. Just enter it as it is.
    128.140.169.0-128.140.169.255
  17. Like
    altoid reacted to JcMagpie in Removing fake customers   
    Any input form on your site that accepts input from a user and stores it in your database is open to abuse.
    You just have to do what you can to secure each one.
    @Jack_mcs  Honeypot lets you pick which pages to cover so should work for most issues.
    If it’s some idiot sitting at a pc with time on there hands doing the spamming ( and there are many doing this) then there is very little you can do to stop them. Blocking IP’s works for a while but the just move to another using VPN’s!
    If it’s bot’s then the honeypot should catch most of them. They look at the code and when they find a form/input filed they dump rubbish into it.
    Honeypots normally add a hidden ( to the user) filed to the page which the user will not see but the bot’s will and they dump rubbish into it which tells the honeypot that it’s not a human and it can block that bot.
  18. Like
    altoid reacted to burt in Removing fake customers   
    Action Recorder
    Could not create_account be protected with an action recorder module ?
    Recaptcha
    Protect create_account with a Recapcha as well?
    IP Address
    Store IP address as part of account creation.  Isn't everyone doing that anyway per GDPR ? 😂
    Back End
    What about a backend page that allows shopowner to drill down customers [and delete them], eg show me;
    customers who registered between X date and Y date and/or have not logged in since and/or have made no orders Self Approve
    How about getting customer to approve themselves (rather than be admin approved).  
    IE, they create account & immediately logged out.  They have to check their email to access a page which "open sesame" their account and access to checkout procedure.  Obviously not right for all shops, but some shops that might be suitable for.
    That's 5 ideas that spring to mind immediately...
     
  19. Like
    altoid reacted to Jack_mcs in Removing fake customers   
    There are several threads regarding this on this subject. There's no simple way to remove them in a stock shop. You can do one of the following:
    If there are not too many, you can manually delete them in admin->Customers. If there are too many to delete manually, you can delete them by editing the database. How easy this is depends on when the accounts were created and if there is something in common with them, like the same in each. To prevent it from happening again,
    If you can determine the country that the accounts are being added from and if you won't sell to that country, then remove the country from the countries list in admin or install an addon or package that blocks countries if your host doesn't provide that option. If you can determine the IP of those that created the account, you could block those IP's. There are addons meant to store the IP if you don't have one installed.
  20. Like
    altoid reacted to raiwa in [Contribution] Ship In Cart   
    Update uploaded:
    Ship In Cart BS reloaded 4.4.
    Changes Vers. 4.4:
      - Fixed shipping method selection if only one module with several methods installed. Thanks to @kanhsu
     
  21. Like
    altoid reacted to BrockleyJohn in [CONTRIBUTION] Ultimate SEO URLs v2.1 - by Chemo   
    Martin, you might be better off with a small change to the standard filter:
    function short_name($str, $limit=3){ $container = array(); if ( $this->attributes['SEO_URLS_FILTER_SHORT_WORDS'] != 'false' ) $limit = (int)$this->attributes['SEO_URLS_FILTER_SHORT_WORDS']; $foo = @explode('-', $str); foreach($foo as $index => $value){ switch (true){ case ( strlen($value) <= $limit && (! is_numeric($value)) ): continue; default: $container[] = $value; break; } } # end foreach $container = ( sizeof($container) > 1 ? implode('-', $container) : (sizeof($container) > 0 ? $container[0] : $str )); return $container; } ie. don't filter any numbers - the change is in the case line in the switch
  22. Like
    altoid reacted to Jack_mcs in [CONTRIBUTION] Ultimate SEO URLs v2.1 - by Chemo   
    A new version has been uploaded with these changes:
    Added code to prevent a strict warning. Found by member @altoid. Changed instructions to give a warning in php 7 and would cause a failure in php 8. Changed more code for compatibility with php 7.2 - add by member @raiwa. See the update file for a change needed in the application_top.php file. Also, I suggest you check the settings for this addon. While they shouldn't have changed I find that one of the biggest things overlooked is the short word filter. Most shop owners, in my experience, leave it set at 3, which may be correct. But if the shop has names that are less than 3 characters. the url may not be as you want and may even be incorrect. For example, if you sell a product named "Ring size 7" and another named "Ring size 8", both will appear as "Ring size" and could be confusing to your customers.
     
  23. Like
    altoid reacted to Jack_mcs in [CONTRIBUTION] Ultimate SEO URLs v2.1 - by Chemo   
    Yet another new version has been uploaded. I forgot to add a fix by @BrockleyJohnin this post. 
  24. Like
    altoid reacted to BrockleyJohn in [CONTRIBUTION] Ultimate SEO URLs v2.1 - by Chemo   
    @Jack_mcs Happy New Year! I trust you haven't worked all the way through.
    A good tip on the settings - it reminds me; one of my clients has the feature to add exceptions to the short words filter, and it's been such a long time I can't remember where it came from. Used it to be part of the addon, or was it extended for them?
  25. Like
    altoid reacted to BrockleyJohn in [CONTRIBUTION] Ultimate SEO URLs v2.1 - by Chemo   
    @altoid you can reduce the number of connections required with a simple edit, in the file seo.class.php, in the database handling class at the top, edit the function ConnectDB so that it is simply:
    function ConnectDB(){ global $db_link; $this->link_id = $db_link; } This makes the class reuse the connection that you already made with tep_db_connect, so each page request only needs a single connection.
×