Hi
I've reviewed the threads I could find relating to images not showing and instead producing a No Images Found link but they seem to refer to 4.7.x and the fix is to run update.php.
As I'm running 4.6.9 that fix doesn't apply and also it seems to be a problem that has developed or cascaded (lovely word) rather than one that existed from the outset, allow me to explain.
I created my first item review with no problems whatsoever. I didn't change anything!
The second one errored but after editing the post by reinserting the ASIN number it reappeared but only if I changed the owner of the post to a user.
The third review, errored the same way but even though I edited the owner of the post again (as that worked previously) the images don't show.
The errors are:
Type php
Date Tuesday, August 15, 2006 - 17:36
User Admin
Location /node/add/amazon
Message Duplicate entry '420' for key 1 query: INSERT INTO node_comment_statistics (nid, last_comment_timestamp, last_comment_name, last_comment_uid, comment_count) VALUES (420, 1155663369, NULL, 2, 0) in /home/walkerst/public_html/includes/database.mysql.inc on line 66.
Severity error
Hostname x.x.x.xI noticed it was creating a node item review and a node for the picture and the latter had comments enabled. Thinking it might be a conflict between the item review having comments enabled and the picture, I disabled comments for the latter but the problem persists.
In addition, under recent posts, neither node appeared. They only appeared in the content listing and I had to delete them from there. I even ran update.php for the 4.6 series but as expected there were no updates.
Does anyone have any suggestions as I'm kind of stuck now?
Comments
Comment #1
Cromicon commentedJust a quick addendum... the images show fine in preview and when you click submit you are presented with an unpublished amazon node withe the item review node published with the No Images Available link. Publishing the amazon node makes no difference and I also tried disabling comments on both and creating a new post with the same results.
Comment #2
Prometheus6 commentedA node for the picture??? I don't have a module anywhere on any system that does that, especially since all I actually get by way of images from Amazon.com is a url.
What modules do you have enabled?
Comment #3
Cromicon commentedGood question... and interesting as I though that was the way it worked. Reason being is when I used import earlier, it imported a bunch of books and created unpublished nodes for each one.
Ok here are the modules:
address
adsense
aggregator
amazon
archive
automember
awtags
badbehaviour
bbcode
block
blog
blogapi
book
bookmarks
buddylist
captcha
cart
comment
contact
dba
event
feedback
flexinode
folksonomy
forum
forward
generic (generic product for ecommerce)
gmap
gsitemap
help
image
image_assist
invite
legal
menu
node
og
ogbook
ogforum
online
page
parcel (ecommerce)
path
pathauto
payment (ecommerce)
phpfreechat
ping
poll
print
privatemsg
product (ecommerce)
profile
remindme
rsvp
search
service (ecommerce)
shipping (ecommerce)
smileys
statistics
store
story
submanage
syndication
system
tangible (ecommerce)
taxonomy
taxonomy_dhtml
term popular
throttle
tracker
upload
urlfilter
user
views
watchdog
workspace
xstatistics
Thanks for looking into this.
Comment #4
Cromicon commentedThis is in the readme and is what I'm referring to as one is automatically created as well as the item review node when an item review node is created.
The node type 'amazon-node' is pure product information.
Comment #5
Cromicon commentedUpdate:
I've disabled all the additional modules including OG taking the site to a barebone drupal install and the problem still remains with the same error.
Comment #6
Prometheus6 commentedI understand what you mean by "node for a picture" now.
I can't duplicate your problem. I did a clean install, imports via the admin function and reviews via q=node/add/amazon. No php errors, no duplication of nid added to node_comment_statistics.
Comment #7
Cromicon commentedWierd.. I still get the errors though. There must be some commonality with others that report the same problem (although there is no mention of watchdog messages in those reports.) I'll keep looking for a solution. Thanks for looking though, it's much appreciated.
Comment #8
MGParisi commentedsorry 4.7 is no longer supported!
Comment #9
Cromicon commentedWell it has been over two years. :/