Jump to content

burt

Team
  • Content count

    14,868
  • Joined

  • Last visited

  • Days Won

    606

Reputation Activity

  1. Like
    burt got a reaction from LeeFoster in 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.
  2. Thanks
    burt got a reaction from mhsuffolk in Facebook Spider overloading site   
    Is it possible to deny access to all pages (except product_info.php) for all IPs in the range 69.171.*.*
    I'm not a htaccess expert, I expect it is possible but I do not know how.
     
  3. Like
    burt got a reaction from cables24h in Idea to use Slugs to produce SEF [ VIDEO ]   
    For the Slug, I assume this is added (eg for a product) in the product adding/editing page in admin:  admin/categories.php
    My suggestion;
    use .js and ajax to query the slug DB table and warn the user if they are attempting to use an already defined Slug.
    Then you can forget the logic SLUG-1, SLUG-1-1 etc. 
    Something like (but obviously for slugs, not email checking);
     
  4. Like
    burt got a reaction from LeeFoster in 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.
  5. Like
    burt reacted to TomB01 in UPS XML 1.7 for Phoenix   
    Well, I have it working!
    It wasn't your post specifics, but the idea you hit upon in the SQL inserts above.  I kept looking at the error codes e-mails that were stating "Missing/Illegal Shipper/Country Code" trying to figure out which was the issue - Shipper or Country Code.  I decided to create log files on the server.  Then I compared the Phoenix log file to my working 2.3.4 log file.  The UPS reply on the working log file was lengthy.  Then I went to WinMerge to compare the two log files exactly.  The 2.3.4 log file had CountryCode "US", the Phoenix log file had CountryCode "United States."  Long story short, my Chrome browser was auto-filling the Admin settings for UPS XML shipping and I accepted "United States" instead of following the instructions that stated Enter the country's two-character code.  What a dummy I am!
    Checked it again, then the error code changed to "Invalid Destination."  I guessed the UPS Server was very smart, so I input my own real address.  It worked.
    Bottom line, the insert into the languages file suggested by Burt fixed the Admin errors about the "UPS_SERVICE_CODE_."  Elsewhere, I had to input into the upsxml.php file, complete path strings instead of the DIR_ stuff, and remove the TABLE_ prefixes and use lowercase database table names.  Then I ensured that correct data was entered into the Admin settings, and used a REAL checkout address.
    Success!
     
    Attached are the modified-for-Phoenix includes/modules/shipping/upsxml.php and includes/languages/english/modules/shipping/upsxml.php files. (Enter your own store's path string where needed.)
     
    upsxml.php
    upsxml.php
  6. Like
    burt got a reaction from ArtcoInc in Spam, Fake accounts and how to stop them.   
    Well meant advice;
    You have multiple hook files performing the catcha routine ... this can be done from one hook file.   
    Take a look at the core bootstrap example where it is placing "stuff" in two different locations;
    https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L23 
    &
    https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L30
    Having just one File with all the hooks (for a given "XYZ" [in this case captcha]) in it, is;
    simpler for you in terms of support simpler for user in terms of having to upload/delete etc
    let us say that the user wanted to not use your captcha anymore, and deleted the file that displays the form...the other files gets missed somehow...they have a broken site.  Not good for them [loss of potential sales], not good for you [support issues], etc etc Hooks are a big part of Phoenix' future, so well done on being one of the pioneers of them.
     
     
  7. Like
    burt got a reaction from ArtcoInc in Spam, Fake accounts and how to stop them.   
    Well meant advice;
    You have multiple hook files performing the catcha routine ... this can be done from one hook file.   
    Take a look at the core bootstrap example where it is placing "stuff" in two different locations;
    https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L23 
    &
    https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L30
    Having just one File with all the hooks (for a given "XYZ" [in this case captcha]) in it, is;
    simpler for you in terms of support simpler for user in terms of having to upload/delete etc
    let us say that the user wanted to not use your captcha anymore, and deleted the file that displays the form...the other files gets missed somehow...they have a broken site.  Not good for them [loss of potential sales], not good for you [support issues], etc etc Hooks are a big part of Phoenix' future, so well done on being one of the pioneers of them.
     
     
  8. Like
    burt got a reaction from ArtcoInc in Spam, Fake accounts and how to stop them.   
    Well meant advice;
    You have multiple hook files performing the catcha routine ... this can be done from one hook file.   
    Take a look at the core bootstrap example where it is placing "stuff" in two different locations;
    https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L23 
    &
    https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L30
    Having just one File with all the hooks (for a given "XYZ" [in this case captcha]) in it, is;
    simpler for you in terms of support simpler for user in terms of having to upload/delete etc
    let us say that the user wanted to not use your captcha anymore, and deleted the file that displays the form...the other files gets missed somehow...they have a broken site.  Not good for them [loss of potential sales], not good for you [support issues], etc etc Hooks are a big part of Phoenix' future, so well done on being one of the pioneers of them.
     
     
  9. Like
    burt got a reaction from TomB01 in Phoenix 1.0.4.0 Admin Pages   
    Nah - exact same happened to me on updating the demo site. 👍
  10. Like
    burt got a reaction from LeeFoster in 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.
  11. Like
    burt reacted to mddel in Product listing   
    Annual subscription has been paid and we wish the team all success with the project
  12. Like
    burt reacted to Dan Cole in How can i automate a SQL update query?   
    I don't know if it's appropriate for your application or not but you could always trigger it on a page call...ie someone visits one of your store pages and the call gets executed.
    Dan
  13. Like
    burt reacted to ArtcoInc in PHP and the newest cPanel   
    I have two live shops. One is running the Community Edition osC v2.3.3.4 (yes, it's that old). The other is running the pre-gold Community Edition osC v2.3.4. I am working on a new site using Phoenix, but that's still in development.
    I had configured my host to use PHP v5.6 on my shops, and everything was running fine.
    My host recently did an unannounced upgrade to the cPanel tool set which, unfortunately, upgraded all of my shops to PHP v7.3. Needless to say, there were problems.
    The first issue I noticed was that I could no longer run the Security Check module in Admin for either shop. I verified that the code against a backup to make sure that it hadn't been hacked. It wasn't until I ran the Server Info module in Admin did I notice that the version of PHP had been changed to v7.3.
    I logged into my host's cPanel, and discovered that the oldest version of PHP available was v7.0. I rolled back to v7.0, but that did not fix the issues I was having. I contacted tech support through their chat function <grumble, grumble>. I explained the problem, and asked if my sites could be rolled back to PHP v5.6. Yes, but not through cPanel. The new version of cPanel only supports PHP versions 7.0 and up. The tech support person was able to roll back my sited to PHP v5.6 by editing the .htaccess file(s) for all of the sites. They are back up and running now. Server Info shows I'm running PHP v5.6, even though cPanel says I'm running PHP v7.0.
    I hope this info may assist someone who may run into a similar issue.
    Malcolm
  14. Haha
    burt got a reaction from azpro in What is the best way to learn webdesign?   
    You might like to speak with Rezoyen
    who, it appears...sits right next to you...
    <cough>spammer alert</cough>
  15. Haha
    burt got a reaction from azpro in What is the best way to learn webdesign?   
    You might like to speak with Rezoyen
    who, it appears...sits right next to you...
    <cough>spammer alert</cough>
  16. Haha
    burt got a reaction from azpro in What is the best way to learn webdesign?   
    You might like to speak with Rezoyen
    who, it appears...sits right next to you...
    <cough>spammer alert</cough>
  17. Haha
    burt got a reaction from azpro in What is the best way to learn webdesign?   
    You might like to speak with Rezoyen
    who, it appears...sits right next to you...
    <cough>spammer alert</cough>
  18. Thanks
    burt got a reaction from bonbec in Terms of Use.   
    There is absolutely no problem with discussions about other carts, so long as the discussion is in the context of us here at osCommerce. 
    For example, there would be absolutely no problem in someone asking;
    At the moment I am using "whatever-cart", I'm thinking about changing to osc...does osc have XYZ feature? And no problem in someone replying;
    It doesn't have XYZ, but if you install osc and then download this addon...you will then have something very like XYZ There is a problem in that person given advice such as;
    Keep using "whatever-cart" It's a matter of common sense.  Does the reply that is being made "help the situation" with regards to osC gaining positivity.  If yes:  post it.  If no:  dont post it.
     
  19. Thanks
    burt got a reaction from bonbec in Terms of Use.   
    There is absolutely no problem with discussions about other carts, so long as the discussion is in the context of us here at osCommerce. 
    For example, there would be absolutely no problem in someone asking;
    At the moment I am using "whatever-cart", I'm thinking about changing to osc...does osc have XYZ feature? And no problem in someone replying;
    It doesn't have XYZ, but if you install osc and then download this addon...you will then have something very like XYZ There is a problem in that person given advice such as;
    Keep using "whatever-cart" It's a matter of common sense.  Does the reply that is being made "help the situation" with regards to osC gaining positivity.  If yes:  post it.  If no:  dont post it.
     
  20. Thanks
    burt got a reaction from bonbec in Terms of Use.   
    There is absolutely no problem with discussions about other carts, so long as the discussion is in the context of us here at osCommerce. 
    For example, there would be absolutely no problem in someone asking;
    At the moment I am using "whatever-cart", I'm thinking about changing to osc...does osc have XYZ feature? And no problem in someone replying;
    It doesn't have XYZ, but if you install osc and then download this addon...you will then have something very like XYZ There is a problem in that person given advice such as;
    Keep using "whatever-cart" It's a matter of common sense.  Does the reply that is being made "help the situation" with regards to osC gaining positivity.  If yes:  post it.  If no:  dont post it.
     
  21. Thanks
    burt got a reaction from bonbec in Terms of Use.   
    There is absolutely no problem with discussions about other carts, so long as the discussion is in the context of us here at osCommerce. 
    For example, there would be absolutely no problem in someone asking;
    At the moment I am using "whatever-cart", I'm thinking about changing to osc...does osc have XYZ feature? And no problem in someone replying;
    It doesn't have XYZ, but if you install osc and then download this addon...you will then have something very like XYZ There is a problem in that person given advice such as;
    Keep using "whatever-cart" It's a matter of common sense.  Does the reply that is being made "help the situation" with regards to osC gaining positivity.  If yes:  post it.  If no:  dont post it.
     
  22. Like
    burt got a reaction from bonbec in Phoenix Announcements   
    Phoenix 1.0.3.0
    Demo Site:
    https://template.me.uk/phoenix/index.php
    Thank you to everyone who helped make this release, for the good ideas, for the chit chat and for the support.
    This release introduces a number of key improvements;
    the foundations of a bootstrapped admin (more to follow...)
    You've asked for it, and now it's coming... revamped categories/products page in admin with product tabs and pre-placed hooks
    supports adding product fields and other content with no core code changes checkout pages with pre-placed hooks removal of deprecated code, redundant pages, functions and features
    Leaner = Simpler = Faster As well as fixing bugs and introducing other minor code improvements... updates version to 1.0.3.0 How to Update if on 1.0.2.8;
    Download this Zip:  1.0.3.0.zip Unzip it Upload it After which;
    Delete un-needed files;
    - admin/banner_manager.php
    - admin/banner_statistics.php
    - admin/includes/graphs/banner_daily.php
    - admin/includes/graphs/banner_infobox.php
    - admin/includes/graphs/banner_monthly.php
    - admin/includes/graphs/banner_yearly.php
    - admin/includes/languages/english/banner_manager.php
    - admin/includes/languages/english/banner_statistics.php
    - admin/popup_image.php
    - includes/functions/banner.php How to Update if on earlier version;
    Find version you are on [admin > tools > version checker] Go back through this discussion and perform updates to get to 1.0.2.8 Then follow "how to update if on 1.0.2.8 & after which" instructions - OR -
    You can download and install a brand new 1.0.3.0;
    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.3.0 Make code changes one by one - THEN -
    After Installation (whether NEW or UPDATE) is complete;
    Visit admin > tools > security checks and perform any needed actions Enjoy using 1.0.3.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.
  23. Like
    burt reacted to Stephan Gebbers in CE-Phoenix v1.0.3.0   
    Ok, got it working. thanks.. and i have installed the admin editor hook now too
  24. Thanks
    burt got a reaction from bonbec in CE-Phoenix v1.0.3.0   
    This release introduces a number of key improvements:
    the foundations of a bootstrapped admin (more to follow...) revamped categories/products page in admin with product tabs and pre-placed hooks much improved checkout pages layout with pre-placed hooks modernisation of Reviews system new Password Forgotten module flags for inactive modules in admin removal of deprecated code, redundant pages, functions and features bug fixes and other minor code improvements LEANER.  SIMPLER.  FASTER.
    Download:  
    https://github.com/gburton/CE-Phoenix/archive/master.zip
     
  25. Thanks
    burt got a reaction from bonbec in CE-Phoenix v1.0.3.0   
    This release introduces a number of key improvements:
    the foundations of a bootstrapped admin (more to follow...) revamped categories/products page in admin with product tabs and pre-placed hooks much improved checkout pages layout with pre-placed hooks modernisation of Reviews system new Password Forgotten module flags for inactive modules in admin removal of deprecated code, redundant pages, functions and features bug fixes and other minor code improvements LEANER.  SIMPLER.  FASTER.
    Download:  
    https://github.com/gburton/CE-Phoenix/archive/master.zip
     
×