Jump to content

aspiringdeveloper

Members
  • Content count

    70
  • Joined

  • Last visited

Profile Information

  • Real Name
    Hydrante Rouge
  1. aspiringdeveloper

    Grid Attributes under development

    Its just that you went from being helpful and constructively criticizing to basically calling my work a piece of shit in the span of 1 day. It may be badly written by your standards but I think the main issue is my documentation was very poor. The contribution itself may need some work. The source code is there if you want. I've agreed with the moderator to leave the contribution up but to place a note that the documentation needs work and most likely the contribution will not work at this time.
  2. aspiringdeveloper

    Grid Attributes under development

    Note to Moderator: Please remove this contribution due to serious problems experienced by users. I cannot maintain this contribution by myself and since all I have received is negative criticism without any debugging support as I have asked, I would like to remove this contribution. I wrote it for myself first of all and thought I'd be nice by sharing. Now that I am being slapped in the face with it I would like it to be removed. Thank you
  3. aspiringdeveloper

    Grid Attributes under development

    Did you use version 1.4- see post 4 above. Use my modded files for a clean fresh install but then overwrite the 2 grid.php files in version 1.4.
  4. aspiringdeveloper

    Grid Attributes under development

    Good news: I've now modded the admin/specials.php and catalog/specials.php to be able to work in conjunction with grid attributes. ;) The bad news is that I am hesitating uploading the upgraded contribution though because I feel that there is a lack of positive feedback about this grid attributes contribution. Either people don't trust it to try it or that the install instructions are sloppy and they fear alot of bugs or interference with there existing mods will hamper them. It's a shame because I know that a lot of you would find it useful. For instance one of the many benefits is that in using grid attributes instead of regular attributes you automatically manage inventory for a member of a product grid. This is unlike simple one-dimensional drop down attributes. With that said I'd like to make a deal with the community here: Would someone please try the grid attributes as it is and provide a positive testimonial that they got it to work, or else help improve it and upload a version 1.4 with changes that they made if they found it to be buggy on there system. I am tired of being the only one saying its working. If the issue is that the install instructions seem daunting and confusing, then can someone update the install instructions in a simple manner so that others will not be daunted. I've spent enough time already on the mod and need a break. I am confident once a few people try this that there will be a major snowball effect. I need some brave soldiers to get the momentum going. When I see some interest from the community I will upload the specials.php modded files.
  5. aspiringdeveloper

    Grid Attributes under development

    That's next on my things to do list. I want to see the popularity of the contribution as it is now go up first as it is. If I invest to much in new features, I may create more bugs and piss off a lot of users. I was hoping for some people to jump in and help out. If someone could check that my file modification documentation works out (FIND xxx REPLACE yyyy) and if not improve upon the documentation, that would help me.
  6. aspiringdeveloper

    Grid Attributes under development

    Mix and match all you want. I do it all the time. Some products have a grid plus attributes, some just attributes, some just a grid.
  7. aspiringdeveloper

    Grid Attributes under development

    Sorry, I tried to make the guide clear. I guess I should have informed myself of the os commerce etiquete for the readme install guides. It could be that its not clear because everyone is accustomed to the format you mention (FINDxxx REPLACE WITH yyy ). However, the pdf guide is actually easier to follow IMHO if you give it a chance. The way to use the guide is as follows: Each file requiring modification is given a snapshot for the file in the relative section of the php file. You can easilly find where to look in the file by looking at the matching text. This mimics the 'FIND' step. The shaded text in the pdf are the inserts required. Where you see strike out text are the text to remove. In summary: Insert shaded text / Remove strike through text Not now but that would be extremely useful - even for me. I think I'll design a grid template function and then the user can choose either to create a blank grid or copy from template. Excellent idea.
  8. aspiringdeveloper

    alternate contact us page

    It sounds about right. If you've made language copies in your language folders for bidform.php and defined all language constats and then changed the include in the main bidform.php within catalog to require(DIR_WS_LANGUAGES . $language . '/' . "bidform.php"); Then it should be fine. I never bother setting filenames constants - its just another hoop to jump through for nothing. forget about modifying filenames constants and change your line: tep_redirect(tep_href_link(FILENAME_BIDFORM, 'action=success')); to this: tep_redirect(tep_href_link("bidform.php", 'action=success'));
  9. aspiringdeveloper

    Grid Attributes under development

    I guess noone is having issues with this contribution or else no one is using it for whatever reason. If there is any hesitation that someone has in trying it, please voice your concern in this thread. Thanks
  10. aspiringdeveloper

    Grid Attributes under development

    Regarding the duplicate key error, I have been able to reproduce it only by brute force. The way in which I re-produced the error is not really a bug but merely the nature of session variables. Let me explain: When I am in product attributes and I create lets say the attribute 'small' for the option 'size'- the system assigns ID #14 for the the next available value option id key. If I then clear my internet cookies or otherwise force my session variables to expire, then try to go back to the exact same screen in product attribute then the script doesn't remember the last variable of 14 for the key. The system still thinks that the a value attribute last assigned was 13 and attempts to make a new 14 only to create a key error. So far I haven't encountered the error through casual use but I'll keep my eye on it. Once again, I cannot test for php4 issues. PS. Feel free to work on my source code to improve the contribution.
  11. aspiringdeveloper

    Grid Attributes under development

    taxable good switching error: Does this happen only when you edit the grid data? I am using the same grid.php as you are. The error could be in the integration with the categories.php file. I am not getting the duplicate key error that you received. It must be another php4 thingy. Can you be more specific? Were you in the products_attributes module or the categories module? Entering the same description for 2 attributes is not a key violation. The tables do no use the description as primary keys. This error must be being caused by something else. Is there another attribute with the ID 14? Normally the system increments the attribute id # for each new attribute so that key violations don't occur. I'll keep an eye on that bug. In my first versions of the edits to the product_attributes.php, the attribute # got reset to 1 whenever the user switched to an empty option. I since fixed that. Maybe there is an error somewhere in your edits to the product_attributes.php file? Possibly I made a typo in the readme. Try to use the pre-edited product_attributes.php that I uploaded. If that fixes the problem, then it means there is an error in the manual edit made to product_attributes.php.
  12. aspiringdeveloper

    [Contribution] Additional Images Module

    WARNING: Major bug in RC2.2 found. If using OsC RC2.2a , and you follow the lazy-man's approach of uploading all changed files, you will not be able to login to the admin panel. You will receive this error: The requested URL /catalog/admin/FILENAME_LOGIN was not found on this server. The reason for the error is that the file catalog/admin/includes/functions/html_output.php as uploaded by this contribution is an older version file that doesn't work well with OsC 2.2a. The solution is to manually change the default RC2.2a html_output.php with the Addtional images changes. PS- I love this contribution! Major added benefit once you get past that bug.
  13. aspiringdeveloper

    Grid Attributes under development

    Shall I assume its working 100% now? Did the V1.4 grid.php fix help?
  14. aspiringdeveloper

    Grid Attributes under development

    Yes this bug was reported before. I thought I had fixed it in the version 1.3 that is uploaded on my server however I may have missed a couple of lines please get Version 1.4 here. You will not find it in the contributions section of the forum until I know for sure from you guys whether this is fixing the problem. Remmeber, PHP5 is not giving me an error so I rely on you guys to let me know and help me to better help you. Explanation: The errors being produced seem to be caused by the foreach() not finding an iterable array. To fix it I have basically added a trap for first checking that an array exists in $_POST['edit']['price'] with the if (is_array($pricedit)){ statement. Try that fix if you haven't already. If it still gives the foreach() errror, then back to the drawing board. $pricedit=$_POST['edit']['price']; if (is_array($pricedit)){ foreach( $pricedit as $gid=>$price){ if (!is_numeric($price)){$price_error="ENTER NUMERIC PRICE"; $err=true; $error['price'][]=$gid;} else{$query="UPDATE products_grid SET grid_values_price ='".$price."' WHERE products_grid_id = ". (int)$gid." LIMIT 1"; mysql_query($query); }}} A few other places I added the test ''if (is_array(..))''
  15. aspiringdeveloper

    Grid Attributes under development

    There have been many alleged bugs bugs reported in the previous thread but none that I can reproduce. The Grid works for me with the following setup: osCommerce Online Merchant v2.2 RC2a PHP Version: 5.2.4 (Zend: 2.2.0) Database: MySQL 5.0.27-standard Server OS: Linux 2.4.31 HTTP Server: Apache If you are experiencing bugs, please specify in as much details the error and your setup. Thank you
×