Jump to content

hughesca

Members
  • Content count

    133
  • Joined

  • Last visited

Everything posted by hughesca

  1. hughesca

    Product Options with Images

    I couldn't tell ya without looking at the files, but it's likely you have an extra ?> in one of the files you modified. I'd check back over the files you made the modifications, she'll be lurking in there somewhere. By it's placement I'd say it's likely in your product_info.php. ;) Peace, Chris
  2. hughesca

    Product Options with Images

    Hey Jack, It's saying that it can't find the file /languages/english/options_images.php. Might want to double check your file locations. ;) Peace, Chris
  3. Hello there! I've updated myQBI to work with OSC v2.3.1 for those that may need it. You can find the updated files on the add-on page. http://addons.oscommerce.com/info/7043 Peace, Chris
  4. I'm happy to say AJAX Attribute Manager works great on the new OSC v2.3.1 with just a few minor adjustments! Here's what you need to do: Step 1. MAKE A BACKUP!!!!!11!!one1 Step 2. Don't talk about figh....oh wait. :D Really though, make a backup...to your local drive...it will save you some day! Step 2. Upload the full attributeManager folder (found under catalogs in the AM download) to your admin folder. Step 3. Using your favorite editor, open up admin/categories.php. If you're using a halfway decent editor (Notepad++ WOOOOO!) you'll want to wander down to about line 244 or so. Here you will see this little fella: tep_db_perform(TABLE_PRODUCTS, $sql_data_array, 'update', "products_id = '" . (int)$products_id . "'"); } Modify it like so: tep_db_perform(TABLE_PRODUCTS, $sql_data_array, 'update', "products_id = '" . (int)$products_id . "'"); } /** AJAX Attribute Manager **/ require_once('attributeManager/includes/attributeManagerUpdateAtomic.inc.php'); /** AJAX Attribute Manager end **/ Right now you're probably nudging your buddy going, "This smartass is just reading off the directions that come with the package!". Ok then Mr. Smartypants...find me <script language="javascript" src="includes/general.js"></script> in admin/categories.php! HA! You can't, because it's no longer there...no, putting it in there doesn't count. Alright, back to topic. As I mentioned above the next part of the instructions call for adding a snippet of code after <script language="javascript" src="includes/general.js"></script> and...well, as I said, it's no longer there. Don't fret though, it's still around...just in a different file. Step 4. So let's take that handy editor and open up admin/includes/template_top.php. Low and behold, there's our little friend (line 38)! <script type="text/javascript" src="<?php echo tep_catalog_href_link('ext/flot/jquery.flot.js'); ?>"></script> <link rel="stylesheet" type="text/css" href="includes/stylesheet.css"> <script type="text/javascript" src="includes/general.js"></script> <!---Hello there! So now we continue following instructions and make it look like so: <script type="text/javascript" src="<?php echo tep_catalog_href_link('ext/flot/jquery.flot.js'); ?>"></script> <link rel="stylesheet" type="text/css" href="includes/stylesheet.css"> <script type="text/javascript" src="includes/general.js"></script> <!-- AJAX Attribute Manager --> <?php require_once( 'attributeManager/includes/attributeManagerHeader.inc.php' )?> <!-- AJAX Attribute Manager end --> Now Harold and his buddies weren't trying to just make your life hell by moving it on ya. To my understanding, they have centralized page headers into a single file, so we no longer have to hunt through 30 different files to do so. Simple. Quick. Easy. Tidy. Now don't go closing admin/includes/template_top.php just yet, we're still going to need it. Step 5. Here they want you snooping around in admin/categories.php again for this little snippet: onload="SetFocus();". Don't waste your time...just like before. It's not there. But where could it be? Go ahead...guess where it is. WRONG (Unless you guessed it doesn't exist AT ALL.) :P That's right...it's nowhere to be found. So stop looking for it already! We're actually going to completely ignore onload="SetFocus();", it's nothing but a tease. Instead let's goto line 44 in our admin/includes/template_top.php we have open still. I know...what a disappointment. Just a lonely <body> tag...all by itself. Did I mention it was lonely? Let's get him some company! Let's take our <body>, dash on a bit of: onload="goOnLoad();" as per our instructions and viola! We end up with this: <body onload="goOnLoad();"> Complicated stuff, isn't it? :lol: It's now safe to save and close admin/includes/template_top.php...we're done with it. Step 6. To finish up, we need to get back to admin/categories.php. Scroll waaaaaaaaaay on down to line 553 where you should find this: <tr bgcolor="#ebebff"> <td class="main"><?php echo TEXT_PRODUCTS_PRICE_GROSS; ?></td> <td class="main"><?php echo tep_draw_separator('pixel_trans.gif', '24', '15') . ' ' . tep_draw_input_field('products_price_gross', $pInfo->products_price, 'OnKeyUp="updateNet()"'); ?></td> </tr> Now pay attention to the word GROSS there as the modification comes after this specific snipit. Put the code from the instructions directly under it, like so: <tr bgcolor="#ebebff"> <td class="main"><?php echo TEXT_PRODUCTS_PRICE_GROSS; ?></td> <td class="main"><?php echo tep_draw_separator('pixel_trans.gif', '24', '15') . ' ' . tep_draw_input_field('products_price_gross', $pInfo->products_price, 'OnKeyUp="updateNet()"'); ?></td> </tr> <!-- AJAX Attribute Manager --> <tr> <td colspan="2"><?php require_once( 'attributeManager/includes/attributeManagerPlaceHolder.inc.php' )?></td> </tr> <!-- AJAX Attribute Manager end --> That it's...we're done! Now go upload your admin/categories.php and admin/includes/template_top.php to your web server and check it out! :o Oh noes!! :angry: It doesn't work! :'( What did you screw up this time? :-" Ha Ha! Gotcha. :devil: (Unless you happen to have QT Pro installed, then it probably worked, but it might not have and if it didn't I can't help you because I'm not using it!) Step 7. If you don't have QT Pro installed you very likely got all excited as it started to work and then ended in a tragic trainwreck of gobbly-gook ending with [TEP STOP]. I died a little inside when I saw it...did you? To fix it, we need to open up admin/attributeManager/classes/attributeManagerConfig.class.php (Say that 5 times fast!). As usual I'll feed ya a line number...maybe I should put them all together and go get a PowerBall ticket? Nah...I actually can't even afford a PowerBall ticket right now. But if you get one with my line numbers and win...please remember me. o:) Ah-hem. Sorry...where were we? Yes...admin/attributeManager/classes/attributeManagerConfig.class.php line number 65 is the one we want. $this->add('AM_USE_QT_PRO', true); Let's change that sucker to false...so it should look like so: $this->add('AM_USE_QT_PRO', false); That's it! Save admin/attributeManager/classes/attributeManagerConfig.class.php, toss it up on the web server and viola! There you have it. AJAX Attribute Manager in OSC v2.3.1. ;) Peace, Chris
  5. hughesca

    [Contribution] STS v4

    Wooohooo! Thank you, thank you and THAAAAAANK YOU! Chapter 7, how did I miss that? LOL After so long, it all becomes a blur. ;) All I needed was to enable info boxes in admin and create infobox.php with <div class="infobox_content">$content</div>! Didn't have to mess with the other contribution. ;) Wow...it's all so clear now, HA! Thank you very much...I'm definitely posting a donation to both STS and osCommerce!
  6. hughesca

    [Contribution] STS v4

    Hello there! I'm hoping someone might be able to point me in the right direction on this one. I'm new to osCommerce and STS, however I've been moving right along with the wealth of information on this forum...however, I've finally hit a snag. Hours and hours of searching and tweaking and I still cannot get past this hurdle. I've got a fresh osCommerce 2.2rc2a install with both Mindsparx Admin and the latest STS contributions installed. My template is very simple, css driven, no html. I squealed with glee when I saw my category box populate! Success!! Hours and hours of studying, tweaking, researching (crying?) and it all comes to fruition...there is almost no greater reward. :D But...for the life of me, I cannot figure out how to get rid of the HTML formatting that either STS or osCommerce is utilizing. Namely the category name text, rounded corners, etc, etc. I've attached a photo below. Is there a contribution perhaps that could just wipe those out for me? :D Thanks in advance!
×