Jump to content
Latest News: (loading..)


  • Content count

  • Joined

  • Last visited

  • Days Won


RusNN last won the day on February 17 2010

RusNN had the most liked content!


Profile Information

  • Real Name
  • Gender
  • Location
  1. Header Tags SEO

    Jack! Please, see on installation instruction for product_info.php line <?php echo '<a title="' . $header_tags_array['title'] . '" href="' . tep_href_link(FILENAME_PRODUCT_INFO, 'products_id=' . $product_info['products_id'], 'NONSSL') . '"/# ' . $header_tags_array['title'] . '">' . $header_tags_array['title']; ?></a></td> This shold be redirect user to top of the page without reloading. But '"/# ' breaks the link and validation too. I think it should be <?php echo '<a title="' . $header_tags_array['title'] . '" href="' . tep_href_link(FILENAME_PRODUCT_INFO, 'products_id=' . $product_info['products_id'], 'NONSSL') . '#' . $header_tags_array['title'] . '">' . $header_tags_array['title']; ?></a></td> After that the link works properly. Same bug for all versions. Am I wrong?
  2. Thank you, Laurent! I miss the addon. May be because its first version is not english. Looks very well. But I think, such functionality should be present in core.
  3. New box system in v2.3.1 is really good. But there is a one little thing, that I suggest. We may now enable and disable boxes, move them from column to column and rearrange, but we can't enable a box on, say index.php and disable it on shopping_cart.php and checkout*.php. Of couse we may change code of the box itself, but we lost mobility. Every new contrib may need a code rewriting. Some folks has hardship with coding. There will be a great if each box has a setting where we may setup number of pages on which a box must not be shown. On admin side it may be looks like a multiselected list with files from www\catalog\*.php in standart setting box (on the right). If we want disable a box n some pages, we simple select those pages in the list. Now on client side in create method of a box we check the setting and a current shop page. If a page will not be found, we process the line $this->group = ((MODULE_BOXES_..._CONTENT_PLACEMENT == 'Left Column') ? 'boxes_column_left' : 'boxes_column_right'); Adding new contribution and styling the shop will be much more easy. There is a contribution that allows multiselected list in admin settings. This functionalitiy may be included into core 2.3.1 and allows to realize above suggession. Sorry my bad english.
  4. AJAX Attribute Manager support

    That's right. As far as I remember there were an old version of AJAX AM which allows to add attributes even if NO product is (product was not saved) in database. This is not correct in my opinion. I dont't carefully see when this feature were disabled, but in my and later version product should be saved (read as it must be present in database) before adding options through AJAX AM.
  5. NEW! Complete Order Editing Tool!

    If you have OE 5.0.8 and high the trouble may be the same as in my previous post to miltenyi. Otherwise, check your scripts, not only OE. They may contain errors that difficult to see on first view. When you press Add Product button in edit_orders_add_product.php your product should be written to database. After this happens OE recalculates stock and shipping. Check your database for newly added products present for the order (table ORDER_PRODUCTS). If no products, the problem is in edit_orders_add_product.php script. Otherwise the issue is in recalculating stock or shipping. This will be hard to deduct but not impossible. You may disable ALL your shipping modules and all not default order total modules. If this is help you to add product correctly, try to enable modules one by one trying to add product after each module.
  6. NEW! Complete Order Editing Tool!

    It is possible. OE 5.0.8 and high contain too many unusable integrations with other contribs. That integrations are done poorely. In most cases to work OE correctly work you should have all integrated contribs installed. I can't carefully support such versions of OE.
  7. NEW! Complete Order Editing Tool!

    What error? What browser? Have you SPPC installed? Does OE work before? Try other browser, IE is good. Check installation of OE. Try to disable SPPC and add new product.
  8. NEW! Complete Order Editing Tool!

    Hi Andy Manual Order Maker create an empty records in database for new order. You may see newly created order in your order list. The Order Editor only takes information provided by the Manual Order Maker. If OE works fine with other orders, so MOM fail to fill proper info in your database. Check installation of MOM, check your database fields. Check information in table ORDERS after you create new order through MOM. The line with orders_id=<NUMBER OF YOUR NEWLY CREATED ORDER> should contain information about your customer. If not, check installation of MOM or ask in proper thread.
  9. NEW! Complete Order Editing Tool!

    What's this? Restore from backup and install OE manually. The autoinstaller for OE is for too old version.
  10. NEW! Complete Order Editing Tool!

    Hi, farbor! Unfortunatelly it is not so easy as it may apper on first look. Each total is calculated automatically by supplied module. We can't simple override that logic or we must make too many mocks in each order_total module. Your way is tempting, but I'm afraid it is not real in way OE works. To implement your way we should realise new field for a variable which will be control CCGV the way you described. After that we should somehow realise logic above... I can't found a solution to it yet. When I realise 2 that posts for other ot modules it took many time to understand how get this modules work automatically correctly. May be I'd like the other way. I just think about and I have no time to think carefully. We may change CCGC order total modules so, it will "see" admin or client side it working. On client side it works as usual, but on admin side we slightly change logic. We will use the varable you spoke and work according to this variable. But this way is only for orders created manually on admin. And we still need a feature that will automatically calculate totals for order which clients makes themselves. This is the real headache. But I think it is possible to implement. Hard, but real. Good idea with a variable!
  11. NEW! Complete Order Editing Tool!

    Here and here you found a solution for only SOME ordre totals modules to work with OE. On one page of the topic I descripbed my point about CCGV issue. There is NO solution to OE + CCGV. And this solution is very-very hard to implement, because too many possible situations may happen if you edit order with Coupon.
  12. NEW! Complete Order Editing Tool!

    Since OE 5.0.7 too many unusable contribs are integrated into OE. Some of them are poorly integrated, but... explain a bit more, what happens after you click Delete checkbox?
  13. AJAX Attribute Manager support

    I'am afraid you are completely wrong. If you want your customers should see any error messages you MUST have QT Pro plugin installed. Ths main difference between QT PRO and AJAX AM is the QT Pro is the system that mainly CONTROL the stock on client side and AJAX AM is the ADMIN SIDE ONLY that allows you EASILY support your products, thier attributes and stock. Both system may be installed separatelly and no one is need the other. But if you want to have more usable interface to control stock on your admin side, you should install AJAX AM at least 2.8.7 version with QT Pro support or later. And if you want you custmers to view messages you should install QT Pro. QT pro has internal tool to control stock on admin side, but it is completely unusable if you have lots of products. AJAX AM allows you to do some more. It replace unusable osC build-in tool for adding products options. So to make your life easy you should have both.
  14. NEW! Complete Order Editing Tool!

    Something wrong with installation.
  15. AJAX Attribute Manager support

    Chris done great work. Congrats! You also make AJAX AM compatible to osC v2.3 and later by doing standart installation except two steps in step 2: 1. In admin\categories.php EXCEPT adding <!-- AJAX Attribute Manager --> <?php require_once( 'attributeManager/includes/attributeManagerHeader.inc.php' )?> <!-- AJAX Attribute Manager end --> add require_once('attributeManager/includes/attributeManagerHeader.inc.php'); AFTER require(DIR_WS_INCLUDES . 'template_top.php'); or MOVE require_once('attributeManager/includes/attributeManagerHeader.inc.php'); exactly UNDER require(DIR_WS_INCLUDES . 'template_top.php'); in case of upgrading from v2.2. 2. Completely ignore instruction of modifying BODY tag to onload="goOnLoad();" . And the last change: 3. In admin\attributeManager\includes\attributeManagerHeader.inc.php REPLACE function goOnLoad() { <?php if('new_product' == $action || 'update_product' == $action) echo 'attributeManagerInit();'; ?> SetFocus(); } with this $(document).ready(function(){ <?php if('new_product' == $action || 'update_product' == $action) echo 'attributeManagerInit();'; ?> SetFocus(); }); So, we just make JQuery to work for us. It runs AJAX AM after page were loaded. We changed only 1 core file admin\categories.php as in original instruction. Tested, works OK. Hi, Sara! I'm sorry, but I completely have no time to made this contrib actually multilingual. To all Hope after New Year I'll find time to make AJAX AM to other version, just because it has some shuffle in versions after 2.8.7 (full QT Pro support) and some bugs are found in them.