Search the Community
Showing results for tags 'convert admin addons'.
Found 1 result
I will attempt to explain what I am doing and what the problem is. I am attempting to convert an existing ADMIN mod for Quickbooks from osC version 2.2 to 2.3.4. For the most part it works flawlessly. It does what it is supposed to do except one small irritating thing. The mod creates what I will call a "sub-menuing" system. There is an file for the includes directory that creates php menu tabs on each page of the mod. Depending on the tab selected a "sub-menu" is supposed to drop down offering additional choices for that particular section. There is a <mod>_styles.css included with required files. Following the suggestions provided here http://forums.oscommerce.com/topic/368538-guide-to-converting-addons-from-22x-to-23x/ I have attempted to activate the styles css file. I have at one time or another left it in the module page_top.php as <link rel="stylesheet" type="text/css" href="includes/<mod>_styles.css"> I have tried it in template_top.php after </head> as <link rel="stylesheet" type="text/css" href="includes/<mod>_styles.css"> I have tried it in template_top.php before </head> with $head_tag .= '<link rel="stylesheet" type="text/css" href="includes/<mod>_styles.css">' . "\n"; $oscTemplate->addBlock( $head_tag, 'header_tags' ); In fact - it was while doing this one that I discovered that the new osCommerce uses the jQuery system and truthfully - I have no clue HOW that affects any of what I am doing. Like I said - the UPDATED module DOES work with 2.3.4, the pages DO what they are supposed to do. I can (and reluctantly have) created individual section ADMIN menu boxes and could do away with the exisitng tabs. My reasoning for NOT wanting to do that is - People accustomed to using the module would find the menu boxes cumbersome and irritating. So HOW can I incorporate the <mod>_styles.css ??? The specific osC v2.2 module is located here -http://addons.oscommerce.com/info/2847 BJ Chadduck