Jump to content


  • Content count

  • Joined

  • Last visited

1 Follower

About Butch

  • Birthday 02/09/1971

Profile Information

  1. Yes you can install this contribution: from the contribution you mention, follow the instructions to install the html editor for the email and newsletter (and mainpage?) but not for the product description (do not modify categories.php). In the ACA instructions you can find how to switch on the html editor (one line to change in categories.php if not already done). It works? Chris
  2. Put configure.php in the /includes folder (rename the existing one before that of course). I had a problem once with this configuration, can be same here. Chris
  3. Comment the following line and you should see the original editor: //$products_modules-> register_module ('html_area.php','products_ms2'); Do you? If not then the problem is not with htmlarea. Do you have a configure.php file in your admin/includes/local folder? Chris
  4. Do you have this in your "new" categories.php? $products_modules-> register_module ('products_ms2.php'); // Add htmlarea 1.7 functionality $products_modules-> register_module ('html_area.php','products_ms2'); From which contribution did you take htlmarea? is it verison 1.7? Is it so that with the new categories.php you don't have any editor? That sounds weird as if there is a problem with htmlarea, at least the old editor should show up. Please note also that htmlarea works only with Internet Explorer >=5.5! Chris
  5. In the admin side, under "Configuration", you should now have a new section "WYSIWYG Editor 1.7" where you can set many parameters. First one should be "Product descriptions use wysiwyg htmlarea?", enable it and it should work. Chris
  6. The parts of contributions that does not involve categories.php must be installed like usually. It means that you have to copy the htmlarea folder to your admin folder and process the SQL file with for example phpMyAdmin. After that you can turn htmlarea on from the admin panel and see it in the product editor. Chris
  7. The ACA module has been added today, check the Margin Report contribution (1594). Chris
  8. Just follow the instructions given in Master Products, here a the file where to do the modifications: When it says: FIND THE FIRST OCCURANCE OF switch ($action) { => this is in admin/categories.php When it says: FIND THE SECOND OCCURANCE OF switch ($action) { => this is in admin/includes/categories_right_panel.php When it says: FIND THIS default: if ($rows > 0) { => this is in admin/includes/categories_right_panel.php
  9. The contribution has been updated to v1.0a, here is the changelog: v1.0a, 7 dec 2004: - Removed registration of categories description module in categories.php as it is not included in the package. (Was giving an error because of missing module) - Added htmlarea 1.7 in the package, no need to dowload it separately. This is used by image_upload category module and html_area product module (which are included in ACA). - Updated install instructions. Known modules at this time: Category modules: - Jpsy image uploader for category image: included. - Category Description (contribution 1373): Find it here Product modules: - htmlarea wysiwyg editor for product description: included. - Jpsy image uploader for product image: included. - Product Extra Fields (contribution 2202): Find it here - Header Tags Controller (contribution 207): Find it here
  10. This is the support thread for the Advanced Categories Admin (ACA) contribution that can be found here: www.oscommerce.com/community/contributions,2611 What is does: - Instead of modifying categories.php for each contribution, modifications are inside modules. - Installing a contribution that have a module is now as simple as copying a file. - Very fast update and installation accross projects having different contributions installed. - 'Old style' installation is still possible. - Works with osC 2.2 MS2 Please note: - The basic ACA package does not give more functionalities than the stock osC, modules need to be installed for that. - Modules can be found with their respective contribution.
  11. Butch

    ACA and Modules

    Few answers: - With ACA, the look of the product/category editor is quite same as the original, some lines are added with each contribution installed. - You can find the modules with their respective contribution. - To use a module, it must be registered at the beginning of categories.php, otherwise nothing will show up in the product editor (That's probably why you don't have Extra Fields and no image uploader). See install instruction given with the modules. - Version 2.3.5 seems to be a valid full package for header tags controller.
  12. Here are some answers: - Empty fields are not displayed in the product info. - If fields are not empty but do not show up, check if they are saved in the database, it can be a problem in the admin installation. - If you use the friendly URL option, take version 2.0b - To have the extra fields showing somewhere else in the product info page, take the code added by extra fields contribution and put it after the "product_description" instead of before. - If you use ACA and have an error with the a line like "register ... category_description.php", just comment the line and read the install instruction to register the Product Extra Fields module inside categories.php
  13. Just comment the line if you are not using the Category Description contribution. This is a mistake in the package. Modules are not included in the ACA contribution because it would be difficult to maintain, but are included with their own contribution. The modules you use must be registered in categories.php, so in your case you must do it for the Products Extra Fields.
  14. Butch

    [Contribution] Extra Fields

    It seems that a previous modification (master products?) eats the $products_id variable. Look at the SQL query: WHERE ptf.products_id= and ptf.products_extra_fields_value<>'' There is no product ID after ptf.products_id= Extra fields won't work without this ID.
  15. Butch

    [Contribution] Extra Fields

    I've just posted version 2.0 of this contribution, which finally supports multi languages. You now have the choice to display the fields in all languages, like before, or only in one. (I mean that each field can be separately configured). Update is quite easy. Post here if any problem.