Latest News: (loading..)

acidvertigo

Members
  • Content count

    277
  • Joined

  • Last visited

  • Days Won

    4

acidvertigo last won the day on December 1 2014

acidvertigo had the most liked content!

4 Followers

About acidvertigo

  • Birthday 01/10/1979

Profile Information

Recent Profile Visitors

29,383 profile views
  1. That's a good news for all us, but where i can download the class?
  2. This is a list to what I think could be added to the list and in general move osc to the same step of competitors: - Admin bootstrapped (big work I know but someone should begin one time GLWalker has started it) - php 5.4 as minimum as 5.3 is at end of life (5.4 should end it's life on summer) - cut drastically code duplication (same functions and class files on frontend and admin side are becoming to be unacceptable for a modern web app). - Multistore support - IPv6 support - functions/general.php splitted in several files as it is more easy to manage code inside (actually this file has inside too many functions with too many separated purpose as for example: date, environment, categories, products, security functions are all inside one file) - Google sitemap - A orm like (not a complete orm) system of classes that can extract more important data from database, for example product, categories, manufacturers, reviews class. ( syntax like: osc->products->findall(); speeds development) This is a huge work I know, and more core related just to ask what you guys think about those points
  3. Not to complain, just a suggestion, but it's not more easy to maintain only one official "Master"? For example now the situation is: Your master: no superglobals, no some code optimization, bootstrap fully implemented, page modules on next level etc. Oscommerce master: superglobals, some code optimization, bootstrap buggy, shopping cart buggy etc. One master with the goods of this two masters can be a good start to develop with it. Or not?
  4. Great news! Only some questions: In which github repository it is possible to send changes? What will happen to official oscommerce github master branch that has already some code improvements and some pull request that are waiting to be merged?
  5. Use ini files could be very nice! What about also to consider a simple php file with array like this? <?php /* ------------------ Language: English ------------------ */ $lang = array(); $lang['PAGE_TITLE'] = 'My website page title'; $lang['HEADER_TITLE'] = 'My website header title'; $lang['SITE_NAME'] = 'My Website'; $lang['SLOGAN'] = 'My slogan here'; $lang['HEADING'] = 'Heading'; ?> This can be faster than the ini files as the file needs only to be included and is already an array
  6. Hello @gadiol i bump this post because I was searching to elaborate the seo url from application_top.php file with "use search safe URLS" on true in admin, and without .htaccess and database edits. on application_top.php at line 88 after // define general functions used application-wide require('includes/functions/general.php'); require('includes/functions/html_output.php'); add: if (SEARCH_ENGINE_FRIENDLY_URLS == 'true') { $link = $_SERVER['REQUEST_URI']; $match = array('action', 'cPath', 'manufacturers_id', 'products_id', 'pid'); $url_array = explode('/', $link); foreach($url_array as $key => $value) { if (in_array($value,$match)) { $_GET[$value] = $url_array[$key+1]; } } } this code permits to make the oscommerce "use search safe URLS" feature working passing the $_GET variables. (this is true for the OSC master on github but it can work also with the current release). The next step could be to generate a slug on the fly in the tep_href_link function and next modify the code above in application_top to understand the actual page slug like: http://demo.oscommerce.com/speed-cruise-control-p-18.html I don't know if i have explained well that idea. To reassume i like to have sef urls modifying only application top and tep_href_link code without change the database or load a lot of redundant classes for pages, this code is not complete i know, i want just to share a possibility. can this be of interest?
  7. Here you can find the installation instruction for 2.2 RC2a http://library.oscommerce.com/Package&en&paypal&oscom23&installation
  8. Have you tried the new Paypal app? http://forums.oscommerce.com/topic/398887-paypal-app-for-oscommerce-online-merchant/#entry1710682 Maybe this update can help you.
  9. Sure can be a next step to add the possibility to translate the configuration. Maybe adding language definition in language file and modify the data in the database. The problem for 2.3.5 maybe is the database compatibility with 2.3.4.
  10. Yeah understand that can be a little tricky. Maybe give the possibility to move header, boxes and footer content modules to Top, Bottom, column left or right position? p.s. this remembers me phpnuke era.... :D
  11. If this is an old contrib i think that inside the addon file you should remove these lines on top <!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"> <html <?php echo HTML_PARAMS; ?>> <head> <meta http-equiv="Content-Type" content="text/html; charset=<?php echo CHARSET; ?>"> <title><?php echo TITLE; ?></title> <link rel="stylesheet" type="text/css" href="includes/stylesheet.css"> <script language="javascript" src="includes/general.js"></script> <script language="JavaScript" src="includes/javascript/spiffyCal/spiffyCal_v2_1.js"></script> <link rel="stylesheet" type="text/css" href="includes/javascript/spiffyCal/spiffyCal_v2_1.css"> </head> <body marginwidth="0" marginheight="0" topmargin="0" bottommargin="0" leftmargin="0" rightmargin="0" bgcolor="#FFFFFF"> <!-- header //--> <?php require(DIR_WS_INCLUDES . 'header.php'); ?> <!-- header_eof //--> and remove these lines <!-- left_navigation //--> <?php require(DIR_WS_INCLUDES . 'column_left.php'); ?> <!-- left_navigation_eof //--> and remove also <!-- footer //--> <?php require(DIR_WS_INCLUDES . 'footer.php'); ?> <!-- footer_eof //--> then add after: require('includes/application_top.php'); require(DIR_WS_INCLUDES . 'template_top.php'); and add to the end before: require(DIR_WS_INCLUDES . 'application_bottom.php'); require(DIR_WS_INCLUDES . 'template_bottom.php');
  12. Hello will be reintroduced the banner as foooter content module?
  13. @@Harald Ponce de Leon This is very nice ^_^ Can it be implemnted for example a json file for http://addons.oscommerce.com/category/Languages ?
  14. Uh oh ok , understand, yes also the configuration db should be made "translable"
  15. Uhm not sure about use the session or db before the install process...