Jump to content
Latest News: (loading..)

Antonio Garcia

  • Content count

  • Joined

  • Last visited

1 Follower

Profile Information

  • Real Name
    Antonio Garcia
  • Gender

Recent Profile Visitors

8,979 profile views
  1. Addon installer concept

    May be I'm wrong but I think almost the 60% osC installations are 2.2. Why they can't update? We all know why, right? 30% 2.3, why? Some new shops with a version with an ongoing increase of goods contributions that does the life easy. The effors that some of you for adapt from 2.2 a lot of contributions confirm my suspects. 5% with 3.0 -> only for intrepid people 5% with 2.4 -> only for intrepid people. Good coding but with very few contributions, I think. IF in 2.4 is easy to add contributions, don need this code/contribution, but 2.3 needs it as wordpress need it or magento needs it, or open cart, etc. A scrip that does a backup to your database is essential. A script that install contributions and help you to keep them updated in a easy way is also essential.... of course in the osC version that I needs... Shopowners want to sell products and don't think in php to much. We like to open our IDE, run our local server or our beyond compare to spend a single evening find why 'this' or 'that' code don't work...
  2. Addon installer concept

    Estimado Piernas: Happy with your proposal!!! How we can help you? It needs to be into core? nooooooooo if it does the life easy to shopowners they simply use it (as they use others contrib). Here, as ALWAYS, we need find a place where find the instructions to make the zip an the extra files to 'order' the installation. My point of view: A contribution needs to add new files and EDIT old (core or not) files, so: * zip file with all the files needed from a /catalog/ dir. * in the root (not in catalog) a .php file that does the install. why not installer.php? You put it the list of 'steeps' for make the installer: -check ver, files permisions, existence of files, etc but also the hooks for add/edit the new code. In a second step, 'We' need study the way to make a log of the orders that 'installer.php' did, may be using a variation of 'Contribution Tracker'. In a future these orders may be executed in reverse to 'unninstall' the addom. I suggest you that you see here: https://apps.oscommerce.com/JWbl5&core-code-of-the-autoinstaller-script https://apps.oscommerce.com/Profile&247516-pektsekye They do almost the 75% of the needes you listed. The only drawback is that the 'list of steps' is written BY HAND in a xml file. If you make a class or a sort of functions that can translate a list of human readable actions (located in an array, for example) to a xml file you will do it! Whe array has 'verbs' that trigger a kind of functions like that: $instrucctions_array = array ( 'action' => 'insertCode', // <-- this verb will trigger the actions listed below 'file' => '/admin/customers.php', 'line' => 56, 'beforWhere' => '<div class="located place">, 'codeToBeInserted' => '<p>A buen precio va el tomate</p>' ) tep_insert_in_cofiguration_table ( $paramName, array $arrayOfBeautifullParams) if needed... tep_insert_in_configuration_table ( $paramName, array $arrayOfBeautifullParams) if needed... tep_insert_in_file_this_code tep_uncomment_in_file_this_code tep_add_in_file_this_hook tep_edit_language_file_with tep_write_in_log_when_installation_is_sucessfull Another suggestion: STOP adding in classes params that almost never are used. Where need we to know the value of MY_N_MODULE_VERSION_NUMBER ? In the modules.php page? If not the infinite number of define()'s will be as crazy as useless, I think) https://generatewp.com/plugin-readme/?clone=test-plugin-readme-txt-file
  3. Check it out ...page editor for oscommerce:

    what exactly means your "hahaha"?

    1. Antonio Garcia

      Antonio Garcia

      Dear Whitehat:

      Only I'm happy with your try!  As there are no way to say  'eureka'  y put 'hahaha'.

      Are you planning to make a contribution? Where I can see your progress? did you open a forum topic?

      I have NO time for help you, but at least , if you need, an spanish.php for this code, contact with me and I will send you the translation.

      By the way, do you tried in the past an attempt to introduce a 'template system'. I also think that you did a github repository with this but I can't find it. Why you stopped making this promising update?

      I (sadly) saw that you have a hidden war with Burt (sorry, I don't want to be obstrusive) but I think that your collaboration with the 'new final oscommerce' should be appreciated.

      I'm not 100% agree with all your propolsal of code changes but I think that it's usual. I follow you because I think that you are doing interesting thinks for osC.

      All my support & respect for your work.

      And remember, your proposals don't need to be accepted for the 'core' in all the cases. For example STS or Ajax Attributes are not core but all of us KNOW that there are/was essential...

      Another example is your 'module maker' that SHOULD BE INTO OSCOMMERCE.com but I think I know why it's not there...:rolleyes:

      All the best from Madrid


    2. wHiTeHaT


      There is no (hidden) war.

  4. Very good entry! My sort reply is 'easy'. ...the long one: Watching the others alternatives of osCom that are the winners... https://trends.google.com/trends/explore?date=today 5-y&q=oscommerce,magento,prestashop,shopify,%2Fm%2F0xpxtgc - Easy installation of contributions / languages / templates. The customer upload a zip file and install it. May be the code used for update the core flies used in 2.4 may be a starting point. Also is needed to decouple core files for 'new files/folders' from app's / contributions. Isolate the core from contributions, isolate the application core from representation (templates). No more search in the branches of directories of directories of directories from our lovely osC for add/edit/delete apps, contributions, languages files or templates files, the ussual issue when someone try to install a new contribution. - Easy installation, creation of templates and avoid coupling/dependency from a framework (bootstrap, jquery). Avoid insert html classes into code that works only in bootstrap. No more js into php, no more css into php, no more echo "<div class="btn"..." or class="col-", etc. If not we can't update to bootstrap 4 easily (right, Gary?) or foundation or material desing or even try to add classes to a new template unless you search into classes or may be a page file or may be an configuration param... - Options/attributes: Need to rethinking how handle grouped options (a T-shirt red XL, printed in back/front), add EAN, weight, dimensions - Admin: Some efforts to make a responsive admin are not fully public (even unkown) for a lot of customers. It's a good news that this will be solved according the 'official roadmap'. Tables that can be sorted (customers, categories), ajax (?), a page for install contributions, etc. - How to handle modules: I think that the recent 'ultra' modularisation of page-components into 'modules' is good but I think someone must start thinking the best way to handle 250 modules in a easy way. The 'modules.php' must be redesigned, Piernas is doing a good try but I think that is only the first steep of a needed complete remodelation of this file. Seeing the admin side of wordpress may help us to thinking in make 'bulk changes' in params instead one by one. - A easy way to update database from previous versios to 2.3: Need for an 'official' script to make an automatic update from previous versions. A recurring issue for a lot of shopowners that would like to try. Yes, I know, there are a sql script, or is easy if you know that mysqladmin exist but is not the regular for a shopowner. The current oscommerce have some scripts that do something with the database but NOT an update from previous versions. If they are in core and they are almost usseless (may be someone uses it ONE time in their entire life) why not add another script of the same nature? - Try to make parallel programing to avoid drastic disruptions from versions: I think is time to learn something from the past. Why 2.4 or 3.0 are a fault versions? Good coding (may be a little cryptic) with new programming paradigms but nobody's use it because the lack of contributions (well, frankl uses it, I know ). I think that 'sometimes' the official osCom development is good for learn PHP but core-developpers don't care if people will use the new or not. You can develop/code as you can/want but is good to see that the others are doing to try to keep customers/coders close. For example the 'new' feature for updating core versions (2.4) must be implemented in 2.3. ... and another NON related comments: - When 2.34 edge will be into the official download page? To much good work hidden in oscure forums links supplied for users... The 99% of people don't use this web as us (searching in every corner for news) but they need a easy way to be informed. - When a (decent) wiki where developers can read how to code, which functions classes exist (to avoid reinvent the reel) ,how name functions, conventions about dir namming, class naming, etc. etc.? - When a (decent) language area where people can contribute to update/edit/download languages apart the english? - When a decent app's area where you can check if a app/contribution is good for you, the osC verssion that can support, the rating by ussers, link for forum, link for bug / suggestions? Why I CAN'T search for UPS or API or CSS?!?!? (please!!!!! decrease the minimun search characters for make the search in the app area)
  5. @@azpro, thanks for your time and code. May be is time to zip all in a addon? I'm not 100% sure but if you zip it in a addom will be easy to find it in the future searching in the 'addons area' instead find it in the 'stratum' forum.
  6. Is anybody there that can check the stats about the more donwloaded addoms to track, for example, the 25 more downloaded in the last year? Can share with us this list? This will help us to know the desires/thougs. At least the same that the thoughts of everyone of us writting here. My grain (focused in the admin area): 1.- As soon as possible, create a core code that can be reusable in every next version. Try to avoid to create a 'wall' between osc and the shopers every time a new verssion arrives ( plus no compatibility of old addoms). 2.- A database import from 2.2 to 2.X. I kow, I know, that this is easy, you can do it in 2 minutes, etc. But I think that the more important for a busisness is the info that it ownes (their customers, their product info...). A trusted addom that import easy your/their sensitive data will be welcome and, may be, a few more people should be seduced to 'go forward', instead to be in the 'Groundhog Day of php 5.2 / osC 2.2'... 3.- Edit all sort of things: orders, cotomers detaills, invoices, products (when ckeditor or something like that will be in by default?) a decent attributes editor, etc. 4.- Sort all kind of pages: customers, categories -> no need to show the tree of categories but ALL the products in a table that would be filtered - if necesary by a dropdown menu-; orders, reviews... 5.- Stock control (including attributes), margin control. And, of course (sorry, I don't think that the following is 'out of topic'): 1.- A decent addoms area in oscommerce where to find your favorite addom, where you can RATE or share with others that 'this addom don't work with 2.3.99' or 'It's is great with a clean interface' and also inform (from developer or users) if this addom are compatible with that osc version, etc. No original (WP users are familiar with that), I know... 2.- The work that Burt and others did in the past year is laudable, but it seems that the BS version is almost a cryptic femonema that only the initianes can find. When will see that GOOD NEWS in <H1> in the very first page of oscommerce.com with a link to invite to download (download me / see all the compatible addons 25 and adding every day). Instead create a entry in this forum to list the BS compatible addoms, why no put in the addoms page at last a 'caterogy of 2.3.4BS' to filter the addoms? Spare time to coding. Perfect! But, at least, all of us (ejem, Your) will like to spread your code to all, right? Open the hive and show the honey!
  7. I want to become a volunteer to translate into Spanish-Spain. (Thanks google translate!) Please, tell me when we start and how collaborate.
  8. May be a seller wants something like that: http://devheart.org/examples/jquery-customizable-layout-using-drag-and-drop/3-implementation-in-a-real-design/index.html even a 'simplified' version of: http://neokoenig.github.io/jQuery-gridmanager/demo/simple.html No more numbers, % or know if bootstrap has 12 or 14 colums. I think. I think that prestashop does somethink like that (a 'live editor' for the front page). A 'live previev' (in products_info or even index - including columns) will be 'the paradise' of all (including coders) :thumbsup:
  9. Product Info CLASS in 2.4

    Dear Luca: You are right and, as I write, your approach is the more 'classic', but I found that this new code AGAIN need to be edited if someone try to add a EAN field of somethig like that. I think this class is one of the heart of osc and it would be a good idea to try to be as 'intouchable' as the 'database' or 'table' (in 2.2) classes is/was. I know that all of the developpers that are now working, try to avoid that the new code has the same 'problems' that the old one (avoid to modify 'core' files for some contribution/s). Only my point of view. If I found an alternative/patch, I try to show it here to be discussed. May be creating a few setters that 'construct' the query? or (not usable code, only an skecht) ;-) $product = new Productclass; $product->fields_products_table_array = array(product_id, price, EAN); $product->fields_products_desc_table_array = array(products_name, products_title, ); $product->use_specials_table = true; $product->array_of_new_tables_to_be_used_in_query = array(table_name, array((fields,...), array_type_query(left join, array(condition of query => p.products_id = newtable.producst_id) $product->perform_query; //manage the arrays and use or not SPECIALS_TABLE to create the query string and perform the query This second approach will help to use only the fields that are needed (not the same in diff. scripts, as mentioned in previous post).
  10. Product Info CLASS in 2.4

    Luca: Congrat for your time and effors! When someone try to add to the PRODUCTS_TABLE and/or PRODUCT_TABLE_DESCRIPTION a new field (a contribution that need it), then he must change not only the php files to show the new field, but also the class inself must be edited to handle it, right? I know that the Burt approach (select * from PRODUCTS_TABLE... and then add to a var) is not so 'cool' as your proposition, but at least no more changes in 'core files' will need. Sorry if I'm wrong.
  11. With css: http://www.minimit.com/demos/bootstrap-3-responsive-columns-of-same-height With jquery: http://stackoverflow.com/questions/9278569/equals-heights-of-thumbnails Example: http://jsfiddle.net/PbfpU/2/
  12. @@burt Yes, I will try to do this. I was so embarrassed about your comments that I try to solve this as soon as possible, spending almost 45 minutes of my work time writting the code without the help of an IDE and without check the code. Only to show that I ony try to be constructive and not destructive. :wub: Thanks for your understanding. :sweating:
  13. @@wHiTeHaT: abuse of store database configuration: Yes, may be but how time takes the database to perform a query with compile all the config. parameters, 0.01 sec.? May be I'm wrong, but may be the problem should be the memory and not the database performance. May be is better to write these kind of params into a file instead in database, a 'file read' was faster than 'query database' but, in this moment this is not 100% true. God thread (database performance)...