Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 12/08/2019 in Posts

  1. 3 points
    ecartz

    Use Search-Engine Safe URLs

    False. Once upon a time, search engines paid attention to things that were in the domain and path but not query parameters. So it made sense to put things like product ID in the path rather than query parameters. But all major search engines (Google, Bing, Yahoo, etc.) can handle query parameters now. It was never quite right anyway and is totally useless now. It just makes it look like you have duplicate pages. The only reason it's still in core is that I haven't deleted it yet. Maybe next month. If you really want better URLs, then install something like Ultimate SEO URLs or similar. That's not quite right. It takes the = signs out too. https://www.myshop.com/product_info.php/sort/4d/cPath/22/products_id/829 What it should do is make it look like https://www.example.com/product_info.php/products_id/829?sort=4d&cPath=22 but it's really an inferior solution. Better to use an SEO URLs contribution so you can get the keyword benefits. E.g. https://www.example.com/stamps.html?sort=4d&cPath=22 Note that Amazon.com does this like https://www.example.com/1989-German-first-class-stamp/dp/[product_id]?what=ever and then just ignores the first thing after the domain. But they only do that for new products. For old products, they leave the https://www.amazon.com/exec/obidos URLs even though Obidos has been turned off for more than ten years. Anyway, when I delete SEF URLs, I plan to make it easier for people to make their own URL Apps. Ideally I'd like to upload SEF URLs as an App in the marketplace.
  2. 1 point
    JcM Google reCAPTCHA V2 & Terms Phoenix A simple add-on to let add the Google reCAPTCHA V2 and accept terms to any form in Phoenix 1.0.4.0 that has the hooks added to it. It is a no core change add-on and uses site-wide hooks. Simply copy all the files over. You will need your Google reCAPTCHA so you can add them to the following file includes/languages/english/hooks/shop/siteWide/jcm_google_recaptcha.php Just open it in your editor and add the comment and keys into it //google define('MODULE_CONTENT_RECAPTCHA_ERROR','Sorry you need to prove you are human first please complete the google captcha'); define('MODULE_CONTENT_RECAPTCHA_SITEKEY','Place your site key here'); define('MODULE_CONTENT_RECAPTCHA_SECRETKEY','Place your Secret key here'); You can also define which pages it is shown on by editing the hook file. $good_pages = ['contact_us.php', 'create_account.php']; This is done in both the capatcha hook file JcMgoogleCapatcha.php and the accept terms file JcMaTerms.php That’s it it should just work. When you go to your contact_us page you should see the Google reCAPTCHA and if installed the accept terms. This will only work on Phoenix. Enjoy. Can be see working on this site
  3. 1 point
    includes/application_top.php lines 42-44: // set php_self in the local scope $req = parse_url($_SERVER['SCRIPT_NAME']); $PHP_SELF = substr($req['path'], ($request_type == 'NONSSL') ? strlen(DIR_WS_HTTP_CATALOG) : strlen(DIR_WS_HTTPS_CATALOG));
  4. 1 point
    Jack_mcs

    Facebook Spider overloading site

    That tool in cpanel does the block by adding the command to he roots .htaccess file so it's there, though it doesn't matter if you see it or not as long as it works. The IP's are usually assigned in a geographically localized area so you should be OK. There should not be any crossover between the US and Asia but it's possible, though probably not very likely, with eastern Europe and Asia.
  5. 1 point
    JcMagpie

    Facebook Spider overloading site

    The Cpanel IP blocker is a very good tool. You can add an IP in a number of ways IP address can be entered in the following formats. Single IP address, E.g. 192.168.0.1 IP address Range, E.g. 192.168.0.1–192.168.0.100 or 192.168.0.1–100 CIDR format, E.g. 192.168.0.1/32 Using Wildcard, E.g. 192.168.*.* Domain Name, google.com
  6. 1 point
    raiwa

    AJAX Attribute Manager support

    Uploaded new package : AJAX Attribute Manager Phoenix 3.1.1 changes: + fixed wrong css definition which caused all text in admin to show reduced. Thanks to @LeeFoster and @Omar_one for the report and testing
  7. 1 point
    raiwa

    AJAX Attribute Manager support

    @LeeFoster, @Omar_one, Just checked and you are right. The css is wrong, it selects any div. The correct fix is this in admin/attribute_manager/css/attributeManager.css line 8: #attributeManager td, #attributeManager div { font-family:'Trebuchet MS' Arial; font-size:12px; } I'll fix it in the next update, thanks.
  8. 1 point
    Omar_one

    AJAX Attribute Manager support

    same here the font size become smaller everywhere when I'm on the product edit page
  9. 1 point
    The ones that remain are the ones that change from store to store. For example, your catalog directory might be in the root at / or at /catalog/ or at something like /shop/. Each store can choose to do something different. Meanwhile, images/icons/ is always images/icons/ -- there is very little reason to ever change it. Even if you did want to change it in the URL, you could use something like mod_rewrite so that the directory structure would stay the same. In general, most of the constant ones have gone, leaving only the few variable choices. I find it rather unlikely that we'd take out more of the DIR_WS values (except possibly DIR_WS_HTTPS_CATALOG). More likely to go would be HTTPS values and USE_PCONNECT. USE_PCONNECT because mysqli does that in the DB_SERVER. The HTTPS values because very few stores used mixed HTTP and HTTPS today. So why support something that no one uses? The two DIR_FS_DOWNLOAD values may go. And STORE_SESSIONS. The following are pretty safe, although the HTTP ones might get renamed (or not): define('HTTP_SERVER', ''); // eg, http://localhost - should not be empty for productive servers define('HTTP_COOKIE_DOMAIN', ''); define('HTTP_COOKIE_PATH', ''); define('DIR_FS_CATALOG', dirname($_SERVER['SCRIPT_FILENAME']) . '/'); // define our database connection define('DB_SERVER', ''); // eg, localhost - should not be empty for productive servers define('DB_SERVER_USERNAME', ''); define('DB_SERVER_PASSWORD', ''); define('DB_DATABASE', 'osCommerce'); DIR_WS_CATALOG is defined elsewhere, but also pretty safe.
  10. 1 point
    I wouldn't say it that way. What should be replaced is " . TABLE_CONFIGURATION . " and it gets replaced with configuration So that the string looks like insert into configuration ( It will sort of work if you replace TABLE_CONFIGURATION with configuration, but it will generate a notice that may appear in the logs. And of course if anyone ever made a constant named configuration, it would break. Normally, I'd recommend replacing $this->icon = DIR_WS_ICONS . 'shipping_usps.gif'; with $this->icon = DIR_WS_CATALOG . 'images/icons/shipping_usps.gif'; Because that will work regardless of where the catalog directory is located. If you use the <> tool to insert code in the forums, it will be easier to tell it from the surrounding text.
  11. 1 point
    Glad you got it sorted. This should not be required but it will depend on your server setup and how you are configuring your store and .htaccess. The test site has Use Search-Engine Safe URLs set to true and it all works as expected. All my links are simple links like https:kuuza.co.uk/contact_us.php I'm not an expert in these url configs but you may need to check how cookies are set in your config. The ceid should only show once if set properly or get rid of it all together.... But as allways check with an expert first.
  12. 1 point
    Jack_mcs

    Facebook Spider overloading site

    I think you will need to block there range of IP's: deny from 69.171.224.0/19 As far as I know, those IP's are just for their bots so normal connections from FB shouldn't be affected. But check it yourself after blocking them and you can't connect, block each IP separately. It is possible to block a number of IP's from just the product page as @burt mentioned but the FB bot doesn't know what your product pages are so it will search the whole site and would still cause a traffic problem.
  13. 1 point
    This can only be done as henry is saying using something like a SLUG as each url MUST remain unique, just using names will not work as site admin can use same name on more than one product by mistake, easy to do when you have 1000's of products. So code will take www.randomstorename.com/categoryname/productname -c-1234 and only show www.randomstorename.com/categoryname/productname
  14. 1 point
    .html is just 5 digits extra. No need to put .html
  15. 1 point
    the slug do more. it not add after: https://www.freeOSC.com/Pears-p-3.html the additional -p-3 it only uses https://www.freeOSC.com/Pears.html There is no check required to read p-3 as a product_id=3 As a slug is unique and returns ( from the DB) the correct ID
  16. 1 point
    Like i said, this is NOT something i want to argument about. I just offer ( or make an attempt) a code that generates SEF url's. I not go in debat if it is required/needed. That is why i made the poll.
  17. 1 point
    raiwa

    Display prices including or excluding VAT

    2.3.4.(1)Bootstrap CE versions are here available: Display Tax Info Phoenix is here: Display Tax Info Phoenix
  18. 1 point
    Has been updated to fix language file path. JcM Google reCAPTCHA V2 & Terms Phoenix
  19. 1 point
    Yes just a silly mistake on my part, when I combined the hooks in to one file I forgot that I updated the language file to place it into the correct path. Simple fix, in public_html/includes/classes/recaptcha.php find line 22 and replace with this line. require('includes/languages/' . $language . '/hooks/shop/siteWide/jcm_google_recaptcha.php'); Should then work. Will upload the add-on shortly.
  20. 1 point
    burt

    Phoenix Announcements

    Phoenix 1.0.4.0 Demo Site: https://template.me.uk/phoenix/index.php v1.0.4.0 fixes a few bugs in the shop side as well as introducing database enabled hooks and the very first step towards a better template implementation, in addition the manufacturers class is now used in more places. On the admin side we have a better bootstrapped layout (header/footer) and a few more pages have been converted to bootstrap tabular layout. We have some more modules, particularly note the "testimonials" page in the shop side is now modular. If you are on v1.0.3.0, it's an easy update. If you are on an older Phoenix, you'll need to get to v1.0.3.0 first before attempting the below steps. A big thank you to everyone who made the release of v1.0.4.0 possible, especially to the Supporters as well as to @raiwa @ecartz and "F Figue". This release introduces a number of improvements; the foundations of an integrated Template System this has been asked for many times over the years, now it's becoming reality... more bootstrapping in admin with more to come in future releases... admin Boxes made 100% modular How to Update if on 1.0.3.0; Uninstall defunct modules;- Social Bookmarks BOX (main module + all installed child modules)- Card Acceptance BOX Delete defunct files (eg using FTP)- admin/includes/classes/rss.php- includes/modules/boxes/bm_product_social_bookmarks.php- includes/languages/english/modules/boxes/bm_product_social_bookmarks.php- includes/languages/english/modules/social_bookmarks/<all files in here>- admin/includes/modules/cfg_modules/cfgm_social_bookmarks.php- includes/modules/boxes/bm_card_acceptance.php- includes/languages/english/modules/boxes/bm_card_acceptance.php Download this Zip, unzip and upload + 1040.zip Run this SQL in (eg) phpmyadmin)+ https://pastebin.com/c7p4WtL2 How to Update if on earlier version; Find version you are on [admin > tools > version checker] Go back through this topic and perform updates to get to 1.0.3.0 Then follow "how to update if on 1.0.3.0 & after which" instructions - OR - You can download and install a brand new 1.0.4.0, obviously making sure not to overwrite your live shop; clicking the green "clone or download" button at https://github.com/gburton/CE-Phoenix or grab it direct from osCommerce at https://www.oscommerce.com/Products choose "download zip" unzip, upload, install - OR - You can diff your files; Find which version Phoenix you are on admin > tools > version checker go to this URL, changing a.b.c.d to your Phoenix version; https://github.com/gburton/Responsive-osCommerce/compare/a.b.c.d...1.0.4.0 Make code changes one by one it'll take you a while, but if it floats yer boat... - THEN - After Installation (whether NEW or UPDATE) is complete; Visit admin > tools > security checks and perform any needed actions Enjoy using 1.0.4.0 - Join the Phoenix Club - https://forums.oscommerce.com/clubs/1-phoenix/ you'll get to see some of the "behind the scenes" work and help to steer future releases.
  21. 1 point
    raiwa

    List of my Phoenix compatible Addons

    Uploaded: Points and Rewards Phoenix
  22. 1 point
    Phoenix users - please get Better Together for Phoenix here: https://apps.oscommerce.com/Apps&amp;XpyA1&amp;better-together-for-phoenix
  23. 1 point
    Demitry

    Multi_Vendor_Shipping new thread

    @ralgiere@phi148@kymation Ray, Bill, Jim, I have done a lot of work to this module to get it fixed, improved, and adapted to BS Edge as well as PHP7.1, however, almost three weeks back my laptop hard-drive died. I just got my new laptop a few days ago and have been working on getting everything back to what I had. This means that the BS Edge release of this addon will take a bit more time. Luckily I had most of my stuff backed up, ...but not everything. Though the most updated files for this addon are on my test server and I will be able to repackage them along with screenshots and much more. The problem I ran into that I could not resolve, before my laptop hard-drive crashed, was that upon proceeding to the checkout_payment.php page, the system would end the session and log me out of my account landing me on the login.php page. I had not resolved this problem and will need to before completing the new release. Any help would be greatly appreciated. And Bill, Thank you for your help on this module, as well as for saying that this MVS addon should be a standard part of every osCommerce release. I wish more people would make an issue of this, perhaps eventually it will not fall on deaf ears. Thumbs up to you for that! Demitry
  24. 1 point
    phi148

    Multi_Vendor_Shipping new thread

    I do have it operational after working with @Demitry on merging all the changes in. I think that Demitry may have been packaging up the changes to post an update to the community. I'm not sure if he has that ready yet or not. If not, it just takes patience, testing and merging ... but it does work :) I think MVS should be part of the base OSCommerce package in my opinion!
  25. 1 point
    @@drillsar @@tmccaff @@dspeak @@opus_uno2001 @@Peace2u @@kushol @—luke— @@nepm Begging your pardon if this annoys anyone, I got the impression you are all interested in upgrading Multi Vendor Shipping to a osc 2.3.4 Bootstrap compatible version. I'm a store owner running MVS (currently 2.2RC2A) for many years now. I'm not a coder, but I am determined. So far my test install of MVS on BS works pretty well except for the shipping estimators; you can see kymation's reply http://forums.oscommerce.com/topic/101973-multi-vendor-shipping-new-thread/page-246 I'm hoping there is some chance of us working together. I don't have a test website set up that is accessible to the public but I'm willing to share that and possibly open the code up on github if there's some interest. Thanks for listening. ~motorcity
×