Latest News: (loading..)

Antonio Garcia

Members
  • Content count

    87
  • Joined

  • Last visited

1 Follower

About Antonio Garcia

Profile Information

  • Real Name
    Antonio Garcia
  • Gender
    Male

Recent Profile Visitors

7,900 profile views
  1. @@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.
  2. 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!
  3. I want to become a volunteer to translate into Spanish-Spain. (Thanks google translate!) Please, tell me when we start and how collaborate.
  4. 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:
  5. 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).
  6. 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.
  7. 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/
  8. @@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:
  9. @@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)...
  10. Sorry, timeout of the blog, I try to put all the code propposed now: @@burt: 1.- I don't want offend anyone. 2.- If someday I became idiot and want to offend to someone in this blog YOU will be the last person that will be the target of my words. Why? You are in this moment the almost ONLY person (in the staff level) that try to clean the 'obsolete oscommerce' to bring it to the XXI. I know that my limitations of the knowledge of your language will cause some misunderstandings. So, from now to the end of times I BEG YOUR PARDON and beg the pardon of everyone that thinks that my writting is frivolous. If you need further comments of explanations from my side, please, send a PM and, sure, we will arrange everything. Now, social and etiquette apart, go to the code: 1.- Goto: osCommerce-2334-bootstrap / includes / modules / header_tags / ht_product_colorbox.php 2.- insert in line 21: // variables for made the life easy to shoppers nº1 var $gutter_that_shopper_wants = MODULE_HEADER_TAGS_PRODUCT_COLORBOX_GUTTER_THAT_SHOPER_WANTS; var $image_width_that_shopper_wants = MODULE_HEADER_TAGS_PRODUCT_COLORBOX_IMAGE_WIDTH_THAT_SHOPPER_WANTS; 3.- In line 28. Wait! Now is NOT 28 but 31... Replace: } with: $this->gutter_that_shopper_wants = MODULE_HEADER_TAGS_PRODUCT_COLORBOX_GUTTER_THAT_SHOPER_WANTS; $this->image_width_that_shopper_wants = MODULE_HEADER_TAGS_PRODUCT_COLORBOX_IMAGE_WIDTH_THAT_SHOPPER_WANTS; } 4.- In line 49 (ok, ok, may be a little bellow!): Replace $oscTemplate->addBlock('<script>var ImgCount = $("#piGal").data("imgcount"); $(function() {$("#piGal").hide();$(\'#piGal\').photosetGrid({layout: ""+ ImgCount +"",width: \'250px\',highresLinks: true,rel: \'pigallery\',onComplete: function() {$(\'#piGal\').css({ \'visibility\': \'visible\'});$(\'#piGal a\').colorbox({maxHeight: \'90%\',maxWidth: \'90%\',rel: \'pigallery\'});$(\'#piGal img\').each(function() {var imgid = $(this).attr(\'id\').substring(9);if ( $(\'#piGalDiv_\' + imgid).length ) {$(this).parent().colorbox({ inline: true, href: "#piGalDiv_" + imgid });}});}});$("#piGal").show();});</script>', $this->group); With: $oscTemplate->addBlock('<script>var ImgCount = $("#piGal").data("imgcount"); $(function() {$("#piGal").hide();$(\'#piGal\').photosetGrid({layout: ""+ ImgCount +"",width: \'' $this->image_width_that_shopper_wants ''\', gutter: \'' $this->image_width_that_shopper_wants '', highresLinks: true,rel: \'pigallery\',onComplete: function() {$(\'#piGal\').css({ \'visibility\': \'visible\'});$(\'#piGal a\').colorbox({maxHeight: \'90%\',maxWidth: \'90%\',rel: \'pigallery\'});$(\'#piGal img\').each(function() {var imgid = $(this).attr(\'id\').substring(9);if ( $(\'#piGalDiv_\' + imgid).length ) {$(this).parent().colorbox({ inline: true, href: "#piGalDiv_" + imgid });}});}});$("#piGal").show();});</script>', $this->group); Sorry, this block is written 'by hand' with no IDE in front of me to check if the "'" added are right or break the js... 5.- In line 66.... replace: tep_db_query("insert into " . TABLE_CONFIGURATION . " (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added) values ('Sort Order', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_SORT_ORDER', '910', 'Sort order of display. Lowest is displayed first.', '6', '0', now())"); } with: tep_db_query("insert into " . TABLE_CONFIGURATION . " (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added) values ('Sort Order', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_SORT_ORDER', '910', 'Sort order of display. Lowest is displayed first.', '6', '0', now())"); tep_db_query("insert into " . TABLE_CONFIGURATION . " (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added) values ('Sort Order', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_GUTTER_THAT_SHOPER_WANTS', '910', 'Gap wetween images (in pixels)', '6', '0', now())"); tep_db_query("insert into " . TABLE_CONFIGURATION . " (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added) values ('Sort Order', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_IMAGE_WIDTH_THAT_SHOPPER_WANTS', '910', 'Max width of the image (in px)', '6', '250', now())"); } 6.- In line 74 replace: return array('MODULE_HEADER_TAGS_PRODUCT_COLORBOX_STATUS', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_IMG_LAYOUT', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_PAGES', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_SORT_ORDER'); with: return array('MODULE_HEADER_TAGS_PRODUCT_COLORBOX_STATUS', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_IMG_LAYOUT', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_PAGES', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_SORT_ORDER', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_GUTTER_THAT_SHOPER_WANTS', 'MODULE_HEADER_TAGS_PRODUCT_COLORBOX_IMAGE_WIDTH_THAT_SHOPPER_WANTS' ); My apologies again. And, please, tell me if someone, apart @@wHiTeHaT, thinks that this 'code' may be is a good idea or not.
  11. @@burt: 1.- I don't want offend anyone. 2.- If someday I became idiot and want to offend to someone in this blog YOU will be the last person that will be the target of my words. Why? You are in this moment the almost ONLY person (in the staff level) that try to clean the 'obsolete oscommerce' to bring it to the XXI. I know that my limitations of the knowledge of your language will cause some misunderstandings. So, from now to the end of times I BEG YOUR PARDON and beg the pardon of everyone that thinks that my writting is frivolous. If you need further comments of explanations from my side, please, send a PM and, sure, we will arrange everything. Now, social and etiquette apart, go to the code: 1.- Goto: osCommerce-2334-bootstrap / includes / modules / header_tags / ht_product_colorbox.php 2.- insert in line 21: // variables for made the life easy to shoppers nº1 var $gutter_that_shopper_wants = MODULE_HEADER_TAGS_PRODUCT_COLORBOX_GUTTER_THAT_SHOPER_WANTS; var $image_width_that_shopper_wants = MODULE_HEADER_TAGS_PRODUCT_COLORBOX_IMAGE_WIDTH_THAT_SHOPPER_WANTS;
  12. @@bruyndoncx: All right, all right!!! So, WHY no add a variable accesible when you install this module (apart of the numbers to define the layout of the images) with a input form where the user may enter a integer that defines the number of pixels to define the space between images? Please, see the attached image. If someone thought in it and he can desing it, we will be able to do the same and much better!!!! :thumbsup: A new module should avoid the this kind of sin of deSINg, Well, if it it is intended to be used by people that don't know the term 'IDE'.... :- https://drive.google.com/file/d/0B-4RD1RGignteEdPTHF4bC1XU0U/edit?usp=sharing
  13. @@wHiTeHaT :thumbsup: As someone said: "Write code as if next person that mantain it will be a psychopath that knows where you lives"...