Jump to content

Leaderboard


Popular Content

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

  1. 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
  2. 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.
  3. 1 point
    Omar_one

    AJAX Attribute Manager support

    same here the font size become smaller everywhere when I'm on the product edit page
  4. 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.
  5. 1 point
    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.
  6. 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.
  7. 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.
  8. 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.
  9. 1 point
    raiwa

    List of my Phoenix compatible Addons

    Uploaded: Points and Rewards Phoenix
×