RObW

Andrew - yes, step one creates the table in your database, so if you don't do it, you would get this error. Best thing to do is to contact your web host and ask them how you can run the meta_tags.sql file. In phpmyadmin, you simply click on your database, go to the SQL tab, and then select the file to run it. Michael - You probably figured it out after nearly a year, but just for completeness... I suspect that you were trying to add a table called 'swift_oscom.meta_tags', which would not be valid. Solution - don't try to create the table manually, just run the meta_tags.sql file, and it will do it properly for you. The error is telling you that the table 'meta_tags' is missing from the database 'swift_oscom'. The table name is just 'meta_tags' (which is a valid name). Cheers Rob

I think there is a bug in the code - when the DISPLAY_REFERRAL_SOURCE variable is set to false (i.e. 'Display Referral options if "ref=###" is set' is FALSE), the referral form is NEVER displayed. The way I understand the functionality, this variable should cause the form to be hidden ONLY if a ref=xxx referal was supplied. If not supplied, the form should still be displayed. This occurs becuase the variable referral_id is ALWAYS registered, even if it is blank. To fix this: In catalog\includes\application_top.php change //rmh referral start // set the referral id if (!tep_session_is_registered('referral_id') || isset($HTTP_GET_VARS['ref'])) { to //rmh referral start // set the referral id if (!tep_session_is_registered('referral_id') && isset($HTTP_GET_VARS['ref'])) { Cheers Rob

Hi Billie, Sounds like you didn't add every block of code - check through your version and the one in the package - there shoud be five code chunks in admin/categoiries.php, each demarked with // RJW Begin Meta Tags Code ------------ Hi Miop, Thanks :) I just compared my 19th April 3.01 verison to the latest (at the moment) 22nd August 3.0a version by Insomniac, and the only differences are: The name of the Meta Tags table variable (was TABLE_METATAGS, now TABLE_META_TAGS). I'm not sure why this change was needed, unless for cosmetic reasons, or perhaps a similar variable was defined with STS contribution causing a confilct...? Maybe Keri or Keith could shed some light on why this was necesary. There is a new file containing the additions needed in english.php - which were previously listed in the Install file So in theory, you should be able to use either version as they will work the same. Cheers Rob

Billie, Check your database tables files: /catalog/includes/database_tables.php /catalog/admin/includes/database_tables.php It sounds like you have deleted the line which reads: define('TABLE_CONFIGURATION', 'configuration'); You do have a backup, right... ;-) ------------------------------------------- Miop et al, I don't know where you got the TABLE_META_TAGS bit / error from - all references in my original 3.01 contribution refer correctly to TABLE_METATAGS. Perhaps another modification (STS/Lindas Header tags?) introduces this other variable and you are messing up the other contrib? I don't know. However, the 19th April 3.0.1 version has been tested and works perfectly with a clean MS2.2 install ... Cheers Rob

Hi Martin, Looks like you are not adding the line to the databse_tables file (item 6 of install instructions). 6) In the following files: /catalog/includes/database_tables.php /catalog/admin/includes/database_tables.php Add: // RJW Begin Meta Tags Code define('TABLE_METATAGS', 'meta_tags'); // RJW End Meta Tags Code Cheers Rob

Hi BD, They should not conflict, as Header Tags concentrates on the products sections of the file and Category

Hi BD, They should not conflict, as Header Tags concentrates on the products sections of the file and Category Meta Tags concentrates on the categories sections of the file. That said, we do not use Header Tags in our store, so I have never tested. For product specific Meta Tags we use the elegantly simple Dynamic Meta Tags contribution. It is a breeze to install and compliments this contribution nicely. In our store, the combination of these two (Category Meta Tags and Dynamic Meta Tags) achieves all our Meta Tagging needs with minimal maintenance (Categories tend to be reasonably static, compared to Products). ;) Cheers Rob

Gomez, On closer inspection - the error implies that you still have elements of the old Category Meta Tags contribution installed - table 'tep_meta_tags' was part of the old contribution. You need to uninstall the old contribution first - simply reverse the install instructions for this old install. Cheers Rob

Gomez - sounds like you didn't add the lines for the database tables (step 6 of install instructions). Marcus76 - sounds like you didn't add the changes to /catalog/admin/categories.php Cheers Rob

Hi, If you haven't already, install my version of the contribution - it fixes this issue and also adds an admin tool. Cheers Rob

I have added a minor release (2.74) to EP to fix a couple of issues in v2.73 http://www.oscommerce.com/community/contributions,500 - Fixed rounding issues with when using prices with tax. - Fixed price with tax in Model/Price/Quantity download - Modified Date Available code to set Null if left empty (instead of setting current timestamp) Thanks to all for the hard work on this contribution and to John (Mibble) for all his hard work in supporting it. Cheers Rob

Apologies if posted already - found an issue with Product Attribute Tax not being displayed in the Product_info page, although it is added when moved to the cart. It looks like this is a small bug in this fine contribution, so cross posting the fix. http://www.oscommerce.com/forums/index.php?showtopic=81255&st=0 Cheers Rob

Apologies for two posts in a row... Been trying to figure out how to add full compatibility for Product Type Options 1.6 (following Matt's hints above), but am struggling as I am not very familiar with this contribution. Can anyone who is familiar with the coding in this contribution let me know the code changes to make to add an extra column for 'products_options_type' in the table 'products_option'. Thanks in advance Rob

Hi John, Thanks - that helped a lot - I now realise that unless an attribute row is complete, it does not get uploaded. I also found that this means that text boxes in Products Options Type does not work if the products_options_values_id is set to 0 (as suggested in POT instructions). So after making sure that the this is non zero and making the price correction indicated earlier in this thread to prevent rounding, all is working great. Thanks again Rob

Hi Matt, Thanks for the reply, much appreciated. When I use EasyPop to download a file, it has the following structure: As you can see, all attributes are listed against both products - which doesn't seem right (esp as they both only have Gift Wrap and Add Gift Wrap attributes, not any of the Size or Color)... the only mod that I have which includes edits to the Products Options/Attributes tables is Products Option Type Feature 1.6. Have been through the EP code and can't see how this would affect... but not entirely sure. Can anyone shed any light on why this is happening? Cheers Rob