A tester working with Ubercart Auction noticed a conflict with Meta tags and posted about it in this issue, namely that values for placed bids are set to zero and therefore never accepted.
As best as I can tell, the issue arises when the user creating or editing a node does not provide text for the "Description" meta tag, so the Meta tags module tries to create its own description - metatags/description.inc, lines 23-27. (If those lines are commented out, everything works fine.) I'm guessing that this is causing the form that UC Auction puts into a node to be regenerated, causing the values posted from the user from the old form to no longer be accepted.
I noticed that this code seems to still execute and therefore cause a problem even if generating a description metatag is disabled on Meta tags' settings page.
Comment | File | Size | Author |
---|---|---|---|
#10 | error_meta.png | 199.26 KB | vip_sa |
Comments
Comment #1
apadernoI have set #465744: Conflict with Ubercart as duplicate of this report.
Comment #2
Devin Carlson CreditAttribution: Devin Carlson commentedI am also witnessing this problem between meta tags and ubercart.
Whenever I utilize meta tag's ability to automatically grab the text for the description meta tag my ubercart product pages do not work.
As I have a lot of content, it really saves time to have meta tag do this work instead of having the author do it manually.
Since the social sharing/bookmarking modules depend on the description tag, support for those features break.
Comment #3
apadernoComment #4
vip_sa CreditAttribution: vip_sa commentedI get the following error after I have instaled Meta Tags:
Fatal error: Call to undefined function uc_price() in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/ubercart/uc_product/uc_product.module on line 1421
And then I cannot see any product in the catalog plus it takes away the vat of the product after purchase.
When I uninstall Meta Tags the errors no longer happens. This is a critical issue for me so please if you can help me.
Comment #5
apadernoVersion 6.x-1.0 code cannot be changed. The development version code has been changed; if you can check it on a test site, you can verify if it creates you any problem. The method used to create the description meta tag (when the module is instructed to create it from the node teaser) is changed, and it should not cause the fatal error anymore.
You can download the development snapshot from http://drupal.org/node/212852.
Comment #6
vip_sa CreditAttribution: vip_sa commentedThank you so very much! I will test it and get back to you with the result.
Comment #7
vip_sa CreditAttribution: vip_sa commentedI get the following warnings.
* user warning: Table 'houseproducts.metatags' doesn't exist query: SELECT * FROM metatags WHERE type = 'user' AND id = '3' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.module on line 882.
* user warning: Table 'houseproducts.metatags' doesn't exist query: SELECT * FROM metatags WHERE type = 'user' AND id = '3' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.module on line 882.
* user warning: Table 'houseproducts.metatags' doesn't exist query: SELECT * FROM metatags WHERE type = 'node' AND id = '1193' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.module on line 882.
* user warning: Table 'houseproducts.metatags' doesn't exist query: SELECT * FROM metatags WHERE type = 'node' AND id = '9019' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.module on line 882.
It gives me a long list of errors on every page and it says on the settings page:
No meta tags have been enable for editing; enable them on the settings page.
but when you go to the settings page they are all enabled. If you go to any page you cannot add Meta tags because the meta tags menu is not there neither is the Description box or meta tags box
Then it disappeared from the modules and I couldn't disable it or uninstall it. I had to put the old nodewords back to disable it and uninstall it. Sorry but this snapshot don't work at all.
Comment #8
apadernoYou probably didn't run update.php; differently, it would have executed the following function:
When you update a module, you always need to run update.php.
Comment #9
vip_sa CreditAttribution: vip_sa commentedI ran update.php and I got the following error:
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT NULL' at line 1 query: ALTER TABLE nodewords CHANGE content `content` DEFAULT NULL in /var/www/virtual/houseproducts.co.za/htdocs/includes/database.mysql-common.inc on line 520.
Plus one Alter table query didn't execute it said Failed to Alter table
Plus this again:
No meta tags have been enable for editing; enable them on the settings page. although they are enabled. I also cannot add meta tags to any page cause the box for adding tags is not visible
Comment #10
vip_sa CreditAttribution: vip_sa commentedHere is a screen shot
Comment #11
vip_sa CreditAttribution: vip_sa commentedThank you so very very much. I installed the latest update (dev 2009-08-01) and it works beautifully.
Comment #12
vip_sa CreditAttribution: vip_sa commentedI now have installed it on my other site as well and I get the following error:
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT NULL' at line 1 query: ALTER TABLE nodewords CHANGE content `content` DEFAULT NULL in /home/gigguide/public_html/includes/database.mysql-common.inc on line 520.
Update #6100
* Failed: ALTER TABLE {nodewords} CHANGE content `content` DEFAULT NULL
* CREATE NEW SETTING VARIABLES
What should I do and should I worry?
Comment #13
apadernoThe SQL query seems to miss part of the code it should contain (i.e., it doesn't change the type of the field as it should).
The query is build from Drupal, and the module cannot control it. I also checked the declaration of a similar field done by Drupal core module, and I don't see any difference.
May you report here the database schema as MySQL sees it? This would help me a lot.
EDIT: Never mind; the code I wrote is (indeed) incorrect. I fix the problem, and commit the fix.
Comment #14
apadernoI fixed the problem in the code.
When you copy the new files into your test site, remember to run update.php, and select 6100 as module update number; in this way, Drupal will run again the update it failed to execute, and will change the field correctly.
Thanks for your report.
P.S. The new tarball archive will be available in about 12 hours.
Comment #15
vip_sa CreditAttribution: vip_sa commentedThank you very much I will install, test and let you know.
Comment #16
vip_sa CreditAttribution: vip_sa commentedI installed the update and ran update.php and selected 6100 for nodewords update and I got this:
* user warning: Table 'houseproducts.nodewords' doesn't exist query: ALTER TABLE nodewords CHANGE content `content` LONGTEXT NOT NULL in /var/www/virtual/houseproducts.co.za/htdocs/includes/database.mysql-common.inc on line 520.
* user warning: Table 'houseproducts.nodewords' doesn't exist query: SELECT * FROM nodewords in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.install on line 109.
* user warning: Table 'houseproducts.nodewords' doesn't exist query: UPDATE nodewords SET name = 'revisit-after' WHERE name = 'Revisit-After' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.install on line 157.
* user warning: Table 'houseproducts.nodewords' doesn't exist query: UPDATE nodewords SET name = 'dc.title' WHERE name = 'DC.Title' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.install on line 158.
* user warning: Table 'houseproducts.nodewords' doesn't exist query: UPDATE nodewords SET type = 'frontpage' WHERE type = 'page' AND id = '' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.install on line 159.
* user warning: Table 'houseproducts.nodewords' doesn't exist query: SELECT * FROM nodewords WHERE name <> 'geourl' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.install on line 186.
* user warning: Table 'houseproducts.nodewords' doesn't exist query: DELETE FROM nodewords WHERE type = 'form' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.install on line 206.
* user warning: Table 'houseproducts.nodewords' doesn't exist query: DELETE FROM nodewords WHERE type = 'robots' in /var/www/virtual/houseproducts.co.za/htdocs/sites/all/modules/nodewords/nodewords.install on line 217.
* user warning: Table 'houseproducts.nodewords' doesn't exist query: ALTER TABLE nodewords RENAME TO metatags in /var/www/virtual/houseproducts.co.za/htdocs/includes/database.mysql-common.inc on line 249.
Comment #17
apadernoThat query fails because there isn't the table it should be renaming. Are you updating a previous version of the module, or are you installing the last version? If you are installing the last version of the module, then you should not run update.php.
Comment #18
vip_sa CreditAttribution: vip_sa commentedThank you for getting back to me so quickly. I was updating a previous version. So what do I do now? Do I have to do anything?
Comment #19
apadernoMay you report which revision had nodewords.module before you updated it?
Also, may you check if the table nodewords is present in the database? Do you have the table metatags?
Thanks for your report, and helping in hunting this problem.
Comment #20
apadernoI guess that the update functions already renamed the database table, and it is not possible to execute the 6100 update. May you check how the field content is defined in your database?
I apology for the problems this is giving you.
Comment #21
vip_sa CreditAttribution: vip_sa commentedI don't mean to sound stupid but how do I do all that you ask of me? I don't have direct access to the database?
What I can say is this. I had nodewords the one of 08-01 installed and then I updated it with the version 08-02 and in the update script I selected 6100 from the select list for nodewords and then updated the database
Comment #22
apadernoIn that case, it was not necessary to select 6100 for the update; if you don't have other errors while using Drupal, then it's all normal.
The error messages you reported before are caused by the fact the update code has already changed the database table, and it is not possible to execute the update once again.
I am sorry I misunderstood what you were saying; in someway I got confused between what you were doing on a site, and what you were doing on the other site.
Comment #23
vip_sa CreditAttribution: vip_sa commentedOk so there is nothing for me to worry about then. Thank you so very much for all your help. It's the quickest and best responses with help I have gotten to date. It's really very cool of you!
Will let you know if I have any more problems.
Comment #24
apadernoComment #25
apadernoAs I didn't hear back, I would guess the problem has been resolved.
Comment #26
Garrett Albright CreditAttribution: Garrett Albright commentedThere's still some conflicts. I ran into the problem in #4 just the other day, in fact.
Comment #27
apaderno@Garrett Albright: What version are you using?
Comment #28
Garrett Albright CreditAttribution: Garrett Albright commentedUbercart 6.x-2.0-rc3; Meta tags 6.x-1.0.
Comment #29
apadernoAs it is not possible to create again the tarball archive for version 6.x-1.0, the problem needs to be fixed in the development snapshot, which is the base upon which the next official release is created.
The development snapshot has been reported to not have the problem; that is the reason this report has been set to fixed.
Comment #30
Garrett Albright CreditAttribution: Garrett Albright commentedAh, okay. So you suggest we install the dev version to resolve this problem? Sorry, didn't think to try that.