Jump to content

Search the Community

Showing results for tags '234'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News and Announcements
    • News and Announcements
  • osCommerce Online Merchant v2.x
    • General Support
    • osCommerce Online Merchant Community Bootstrap Edition
    • Add-Ons
  • Development
  • General
    • General Discussions
    • Live Shop Reviews
    • Security
    • Developer Feedback
  • PayPal's Announcements
  • Sage Pay's Announcements
  • Solomono - new level osCommerce templates's Announcements
  • German Community's OSCOM v2.x
  • German Community's Allgemein

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Real Name




Found 1 result

  1. As usual, I try to do things a little differently to come up with a solution that works for me. I want to see how my webshop looks like when using bootstrap and also understand the significant differences. I have a clean install of a recent BS edge pulled into a server directory with git so I can keep it up to date easily. I created a git branch so any little tweaks I do (like $_POST vs $HTTP_POST_VARS) I can separate out and ignore when comparing files. I created a bs_configuration and bs_configuration_group table in my real database from the bootstrap oscmmerce.sql script. modified the TABLE_CONFIGURATION to point to bs_configuration and TABLE_CONFIGURATION_GROUP to bs_configuration_group, both on the admin and shop site. Amended configure.php file, both sides, to point to the real database. (As usual, since my site is dual language, I also had to copy language directories just to get up and running properly.) The products are shown on the site, but the header/footer etc are missing. Tried installing but this wasn't working. Found that several of the more recent modules have the configuration table hardcoded in the installation routines. So, I did a search_replace for 'insert into configuration ' to 'insert into " . TABLE_CONFIGURATION . "' as well as the 'delete from ...' statement. I understand for the ease of development and installation of new stuff, it is better not to have to add TABLE_xxx mappings, but currently it is a mix, and confusing. Personally, I would like to ask everyone to keep on using the TABLE constructs until it is officially droppped.