About

CSS-OSCommerce documents the development of www.niora.com, which runs on the OSCommerce shopping cart version 2.2RC2a updated to OSC to CSSv2. Many useful tips, tools and techniques developed for OSCommerce and used on the Niora website are posted here.
We welcome your observations, comments and suggestions.
Niora created:

  1. The first complete CSS conversion for OSCommerce 2.2RC2a, OSC to CSS
  2. Pioneered the incorporation of the 960 grid system into OSCommerce by adapting the grid system to OSC to CSSv2. The 960 grid system has since been officially adapted for OSCommerce v2.3.
  3. Mail Manager, the OSCommerce add-on for shared hosting website bulk email marketing
  4. OSC Mobile, OSCommerce for the IPhone and other smart phones

17 thoughts on “About

    1. Open up includes/application_top.php, look near the top about line 23 and you will see the version of OSCommerce you are using. My guess is you are using 2.2, which has been superceded by 2.2RC2a and now by 2.3.

      Personally I recommend OSC to CSS v2 (which is built on OSC 2.2RC2a). It’s much better than OSC to CSS v1, which is the version you probably got from Github. OSC to CSS v2 will be far easier to install on your site than OSCommerce 2.3. Plus OSC to CSS v2 if I may say so myself has a far easier to grasp conversion from the tables to the 960 grid with divs. 2.3 is just too different, and OSC to CSS v2 has a lot of the features in 2.3. What 2.3 does do is upgrade a some security features, but you can do this on your version on OSC to CSS v2 by following this

      Good luck, and come back and show us the site when you get it done. I’ll put a link to it here.

  1. Hello.
    I am surprised. Very and really good work, and fast deployment.
    Thank you and congratulations.

    However I have some issues perhaps you could help me with, and avoid to review the whole scripts for mobile:

    – My website is in Spanish. The database is Latin 1;
    when I connect to the normal site, it works fine and the special chars are well formed, I mean (í, á, and so on), but when I connect to the mobile site, I don’t see well formed the chars, receiving the typical “question mark” or simmilar.
    As well as this issue, I don’t receive search results if I write with this chars.
    Where can I force the script to work in a specific code page.

    – My descriptions are long…. it is necesary.
    For this reason they don’t fit the normal size for the results and all is bad formatted. What do you suggest as better solution, because I am thinking about trim the string.

    I cannot send you a link to the web site because it is running in a development server, but I can send you some logs or images if you need.

    Again, thank you very much and congratulations.

    Juan

    1. I have stripped out the language files from the mobile oscommerce program in order to reduce the size and speed up the program. The text you are reading is written directly into each page. To deal with this issue you will need to reinstall the language files, or change the text in each file, or perhaps try using a different doctype.

  2. Thank you.
    I have solved it in a easy way.
    Just change the mobile_application_top.php

    $meta_equiv = ”;

    and just running.

    I am having right now some more issues some of them, solved 🙂

    i.e.
    * mobile-cart.php doesn’t work if in the database you have some payment modules installed but not visible: the script fails.
    workaround: uninstall all the payment modules that are not shown, and begin working.

    * paypal express:
    as alternate payment method, it is displayed the Paypal button at the bottom in mobile-cart.php
    but it doesn’t work. After few seconds it is redirected to the uri: shopping_cart.php?error_message=
    and goes directly to the normal website… researching why.

    * Login and create account:
    it doesn’t work
    I have seen you have two lines:
    // if (isset($HTTP_POST_VARS[‘action’]) && ($HTTP_POST_VARS[‘action’] == ‘process’)) {
    if (isset($HTTP_POST_VARS[‘action’]) && ($HTTP_POST_VARS[‘action’] == ‘process’) && isset($HTTP_POST_VARS[‘formid’]) && ($HTTP_POST_VARS[‘formid’] == $sessiontoken)) {

    in a rapid test I have uncommented the first one and I have commented the second, and it works for create account (only for USA 🙁 ) researching why.
    Perhaps could be a good idea adding a listbox to select the country here when creating the account.

    I am really interested in this project, so I am going to work to improve it, and do a lot of comments (I am not a php guy, nor a developer. Just a systems tech with a family store, but very interested).

    I don’t know if you agree receiving posting this things here or perhaps activate the wiki, forum in google where the project resides….

    Some suggestions are welcome 🙂
    Regards,
    Juan.

    1. Good work. I’m glad you found a solution to the language issue.

      // if (isset($HTTP_POST_VARS[‘action’]) && ($HTTP_POST_VARS[‘action’] == ‘process’)) {
      above is the standard line found in OSC 2.2a

      if (isset($HTTP_POST_VARS[‘action’]) && ($HTTP_POST_VARS[‘action’] == ‘process’) && isset($HTTP_POST_VARS[‘formid’]) && ($HTTP_POST_VARS[‘formid’] == $sessiontoken)) {
      This is a security update from 2.3 Perhaps needs more work. The first line is just fine to use.

      You should have little problem using the mobile-oscommerce with any of the payment modules, however, I typically only use authorizenet.

      This is best place to comment on the mobile-oscommerce.

  3. Hello.
    I am confused.
    I have read the documentation, even your code and it looks the script can work with USU5 by FWR Media.
    I have tried to do it work together but always fails.
    My problem is that when an user find a page on my site, i need to redirect him to the right page in mobile site, but i am unable to make it working with USU5.

    I have tried your site and it doesn’t work neither.

    How have you solved it?

    Regards,
    Juan

    1. You can use the ‘smartphone detection’ to automatically direct the smart phone users to the mobile site, but the user is directed to the index or home page. It would take additional coding on each regular page to have it direct to a specific mobile page.

  4. Hello.
    I have been able to have the mobile site working with USU5 just reviewing the installation instructions: the scripts I downloaded from google-code had one step of the USU5 installation unfinished.
    Just adding this part and it begin working.

    Regards,
    Juan

  5. Hi, great job with this! Do you recommend using osc-css v2 code or starting with Osc 2.31? I’m updating a 2.2rc2a store that’s pretty well hacked up. It wasn’t clear from your comments on the contribution. Thanks much!
    John.

    1. I would recommend OSC-CSS v2. Since you have already made a lot of changes, switching to OSC-CSS v2 is far easier. To begin with you don’t need to change anything in your existing database or admin. On the catalog side, the only thing that changes is the html. The programming is the same. Your challenge would be limited to cutting and pasting your catalog side modifications to the same catalog page in OSC – CSS v2.

      OSC 2.3 has some security updates, but these are limited and not that difficult to incorporate into any existing 2.2RC2a or OSC-CSS site. They are here

      The big changes in 2.3 from 2.2RC2a have to do dumping the tables, adding JQuery functioning and making it easier to make design changes from the admin. OSC to CSSv2 does this and more, except for the new admin stuff. However if you are working on your own site, and are familiar enough with how to ‘hack it up’ then you are probably making design changes in the CSS and the html of the catalog pages.

      You’ll gain nothing in speed, and add to the complexity to switch to 2.3.

      1. Excellent, thanks for the quick reply. I’ll go with osc-css v2, that appears a no-brainer. Any chance you could throw osc-css v2 on Github? More developers could share code and hacks there with their own forks of it. But I leave this up to you and if you have time. You have done alot here and its a great contribution to open source.
        Kind regards,

        John

        1. Posting to github is a good idea. I have already posted the Mobile Oscommerce version on github. My problem is that my real business is selling stuff on my own website, but I prefer doing the programming and web design. So when I get something to where I can use it, I have to make myself stop. As a result I haven’t upgraded the OSC to CSS v2 that’s on the OSCommerce site in a while. However, I would be perfectly fine with you posting OSC to CSS v2 to github. Just make it a bit better and post a link or two to back here, and maybe also to the github Mobile OSCommerce page.

  6. hi
    very pleased with your work, though i have some problems with the USU pro 5 and the mobile website.
    i get this error:
    Fatal error: Call to a member function store() on a non-object in /usr/local/www/all/heveababy_live/docs/includes/modules/ultimate_seo_urls5/main/usu5.php on line 78

    You had any other user report this problem?

    Also – i wonder if its possible when using the redirect for mobile users like you suggested, to have a link in the mobile site, where customer can choose to view the “normal” site?

    Right now it constantly redirects me back to the /mobile-index.php 😉

    Thanks
    Mike

Leave a Reply