Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 06/12/2019 in all areas

  1. 2 points
    Dear @peterbuzzin, @MrPhil , @Hotclutch thank you very much for your help. The RewriteRule : RewriteEngine On RewriteBase /catalog/ RewriteRule !^admin($|/) https://www. newdomain.com%{REQUEST_URI} [L,R=301] did the magic impeccably. The problem I had was that the other RewriteRule in the old domain (on the old hosting) they were interfering. I deactivate the old RewriteRule and voilà!!! Best regards. Valqui
  2. 1 point
    BrockleyJohn

    TYOP - BS4

    I use sourcetree ... once you've got it set up with your project you can merge in any further changes to master and just deal with any conflicts
  3. 1 point
    BrockleyJohn

    TYOP - BS4

    to what are you referring?
  4. 1 point
    Fantastic! Glad it's all working for you now
  5. 1 point
    Auto Update Currencies V 1.0
  6. 1 point
    raiwa

    Optional Related Products, Version 4.0

    Hello @Rwe, ht_product_schema is a core module and can't therefor take in consideration the related products add. Schema tags are constantly updated. I'll have a look and try to address this for the next update. Anyway I would say it's not really very important. Thank's for the report anyway.
  7. 1 point
    Morning, So it sounds like you have two hosting environments? Each with their own separate .htaccess files? If the above is true then you'll need different rules in both those files (not the same rules), otherwise you'll cause a infinite redirect loop. If you have the 301 redirect in both files then that could be the cause of the internal server error. In your old site you only need the following: RewriteEngine On RewriteBase /catalog/ RewriteRule !^catalog/admin($|/) https://www.newdomain.com%{REQUEST_URI} [L,R=301] Because it's only purpose now is to redirect all the traffic to the new site (apart from /admin). Also if you're using RewriteBase /catalog/ then you may only need to have the last line as.. RewriteRule !^admin($|/) https://www.newdomain.com%{REQUEST_URI} [L,R=301] Because it's using the previous rule (RewriteBase) as a base/starting point for proceeding rules. So experiment with "catalog/admin" and then just "admin". Then in the new site you'd have this: RewriteEngine On RewriteBase /catalog/ RewriteRule ^(.*)-p-(.*).html$ product_info.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-c-(.*).html$ index.php?cPath=$2&%{QUERY_STRING} RewriteRule ^(.*)-m-([0-9]+).html$ index.php?manufacturers_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pi-([0-9]+).html$ popup_image.php?pID=$2&%{QUERY_STRING} RewriteRule ^(.*)-t-([0-9]+).html$ articles.php?tPath=$2&%{QUERY_STRING} RewriteRule ^(.*)-a-([0-9]+).html$ article_info.php?articles_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pr-([0-9]+).html$ product_reviews.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pri-([0-9]+).html$ product_reviews_info.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-i-([0-9]+).html$ information.php?info_id=$2&%{QUERY_STRING} If that still doesn't work then please do as MrPhil suggested and post contents of both your .htaccess files and we'll soon get to the bottom of it.
  8. 1 point
    Sorry, you have to apply also these previous updates: https://github.com/gburton/Responsive-osCommerce/commit/737363f01b1135cc42f2ae90577da7e2520df72b https://github.com/gburton/Responsive-osCommerce/commit/0e7f0879e56ca68b363232efcdc8ba079fb03f8a https://github.com/gburton/Responsive-osCommerce/commit/003c59b91239de501ee5482cb903e95de696b5ee
  9. 1 point
    It has been included in EDGE at a later point after the FROZEN release. See: https://github.com/gburton/Responsive-osCommerce/commit/20dd3c7d643490d05e3efa5428aacaf4d11132c9
  10. 1 point
    mhsuffolk

    Updated Stripe payment module

    Using that logic why does anyone use PayPal?? That said I am prepared to help if I can. I cannot give you access to my account dashboard but I could possibly give you Keys to do test transactions and, at a suitable time convenient for both of us, give you live feedback as to results. Here is the Stripe page with the coding changes, it is way above my paygrade. https://stripe.com/docs/payments/payment-methods The current code I believe uses tokens
  11. 1 point
    Fixer works only with EUR base currency. Pleasae see this post:
  12. 1 point
    SCH_001

    how to manage heaps of images

    Many thanks @JcMagpie just copied yours and added my small changes back in to the file - all working
  13. 1 point
    Can you show us the full .htaccess file on both sites, and which directory they're in? ***-out any sensitive information. You don't have anything on your new site redirecting back to the old site, do you? Your description of what is happening is very confusing. Is this happening on the old site or the new site? If it's on the new site, it should have nothing to do with the redirection from the old site. Are both sites on Apache servers, or did you change server types?
  14. 1 point
    so how did you put it down in htaccess that it throws the error ? I think it could be like this, but not 100% sure: RewriteEngine On RewriteBase /catalog/ RewriteRule ^(.*)-p-(.*).html$ product_info.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-c-(.*).html$ index.php?cPath=$2&%{QUERY_STRING} RewriteRule ^(.*)-m-([0-9]+).html$ index.php?manufacturers_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pi-([0-9]+).html$ popup_image.php?pID=$2&%{QUERY_STRING} RewriteRule ^(.*)-t-([0-9]+).html$ articles.php?tPath=$2&%{QUERY_STRING} RewriteRule ^(.*)-a-([0-9]+).html$ article_info.php?articles_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pr-([0-9]+).html$ product_reviews.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pri-([0-9]+).html$ product_reviews_info.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-i-([0-9]+).html$ information.php?info_id=$2&%{QUERY_STRING} RewriteRule !^catalog/admin($|/) https://www.newdomain.com%{REQUEST_URI} [L,R=301] Rewrite ^(.*)$ https://www.newdomain.com/$1 [R=301,L]
×