Hi
I have been slowly dealing with some problems created by upgrading to 7.10 from 6.22 and I'm making some progress, though there are still some significant issues.
I wanted to create a custom error page telling users image locations (because failure/no success yet to convert the image module to the D7 form, following provided instructions, etc), are currently invalid, though the problem is being worked on, etc only to discover the "Create" page, article & other content links were missing from where I expected them, under the existing "Create content" link category. I found them directly under "Navigation", later.
The only link that was under "Create content", was "Create event". Ridiculously, because the content type "Event" was based on the D6 event module, which has not been upgraded, I had DELETED that content type after upgrading, but the create event link was left behind. The other ones had been relocated as said!
Under "Navigation", if you click one, like "/node/add/page", everything seems to go well until you submit.
I keep getting such an error:
Notice: Undefined property: stdClass::$fid in file_usage_add() (line 657 of /home/que1/public_html/abc/includes/file.inc).
PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'fid' cannot be null: INSERT INTO {file_usage} (fid, module, type, id, count) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4); Array ( [:db_insert_placeholder_0] => [:db_insert_placeholder_1] => file [:db_insert_placeholder_2] => node [:db_insert_placeholder_3] => 541 [:db_insert_placeholder_4] => 1 ) in file_usage_add() (line 664 of /home/que1/public_html/abc/includes/file.inc).
The website encountered an unexpected error. Please try again later.
Same thing for the "article" content type, I had from D6. Could there be a conflict in this case with the D7 "article" content type?
For another custom content type on the other hand, with cck fields, that had been upgraded using the content migrate module, I noted creating content was possible.
How on earth does one solve this? This is a production site ...
During the initial upgrade process, with only the recommended system core modules enabled, there were no errors. Issues started coming up which involved third party modules.
I'd appreciate any help.
Comments
Help desparately needed!
Hi
After not getting a response for a while, I decided to re-do the upgrade, assuming the existing "article" content type might be part of the problem, since I reason D7 comes with such a content type, i.e. article & page.
So I went back to D6 & renamed the content type to something different.
I deleted all content types, including "event", whose modules did not have D7 versions. The upgrade went smoothly, following the upgrade instructions.
I later enabled the non-core & contributed modules.
The custom content types/fields where correctly migrated using the content migrate module.
It happens to be that I had moved the "create this particular content type" link from the where the rest are to a separate menu.
Why I am saying this:
Most of the other "Create ..." links had been left together BUT during the upgrade, that menu block was not migrated in both upgrade process as it was.
Only the "Create event" link was, although ridiculously, I had DELETED the "event" content type this time before upgrading!
The other add content links had been moved to "Navigation".
When trying to create page content I still get this error:
The page content is apparently posted but you have the error message below above it:
Notice: Undefined property: stdClass::$comment_count in comment_node_page_additions() (line 727 of /home/que1/public_html/abc/modules/comment/comment.module).In some cases, I noted ONLY THE TITLE is posted.
As mentioned for one specific custom content type, creating content is no problem, no errors. For the rest, including "page" & the re-named customed content type I get those errors.
Other notes:
The "Add content" link "/node/add" in toolbar menu does NOT lead to where you choose the content type. Instead it points to "/node/add/event" although as said the "event" module/content type were uninstalled/deleted before upgrading.
So if you click "Add content" link you get this error:
So what I do to get rid of these errors?
I think this is a SYSTEM error, if something goes wrong with migrating parts of the menu (create content), or not being able to create a page or something going wrong related to the comment module as suggested in the error messages.
I would greatly appreciate any help so I get the site back online. I need to post content ...
(I'm not a coder)
Kind regards
Your posts are rather long :P
Your posts are rather long :P
I have encountered this type of problem. Did you use the CCK migrate module?
If so, and you still have a problem, my advice is to create a new content type exactly like the old one if possible. When you want to create new content, use the new type.
If you really need to debug the problem because you really need the content types to remain the same (or because you are very keen on keeping your database clean, which is a good thing!), check that the available fields in the migrated content type are the same as in the old equivalent.
After a Drupal 6>7 upgrade there are often bugs of this kind. You need to pick them off one by one, and you might get better response on the fórums by posting them one by one. Unfortunately upgrading Drupal is often a big job.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors
Hi Thank you very much for
Hi
Thank you very much for your response.
Yes, I realize the posts are long, but I thought it's necessary to give details of exactly what happened. Sometimes because of time difference & other reasons, you may get a reply that may need explaining oneself further or have questions & if at that time you are not online, it means waiting a long time after such an update, before getting the final answer, assuming the issue is followed up.
In the second post, I had explained what I had tried to do after the first.
Yes, if you mean the content migrate module, yes I used it. It showed no errors if I remember well. That's how I get one of the custom content type's content showing with no problem. For the page, recipe module-based and another custom content type I had initially called "article", but in the second upgrade attempt renamed, I had added at least one field using cck.
Creating NEW content types, sounds good, but in the case of the recipe module, which plays a big role, I don't know how that would work.
It seems the error is in the Drupal system I think, if even stuff like the "Add content" /add/node link does not work, because it's pointing in the wrong place, a browser cannot find (The page isn't redirecting properly).
With the "Page", & the rest, may be I might try out that if everything fails.
Does it mean creating new content types has been the only working alternative for you? I have 3 years of posts ... :(. Quite frustrating.
Regards & thank you for the time.
You have been at Drupal
You have been at Drupal longer than me, all I can do is share my upgrade experiences. I had the same problem with the links for add content not working after upgrade, and I never worked out a solution. It has to be something to do with menu paths and in theory should be fixable by direct editing of database but I did not succeed. It is surprising there is not a discussion of it on d.o. Maybe there is and I missed it.
My experience of upgrade has been that the you end up with a lot of database debugging to do. Wherever possible I would look for a solution via the Drupal browser interface because direcect editing of the database can create fresh problems, but direct editing is sometimes unavoidable. So removing and recreating a content type is a route I would personally prefer to debugging the database directly, if it is a realistic option.
The other point would be to fully uninstall any module you do not absolutely need, and clear out as much crud from the database as possible, before going for a D6 > D7 upgrade. Wherever possible, rip out / replace any module or field without a good upgrade path.
I have no really specific answers. As you know, there some bugs in Recipe module. It may be worth researching whether the dev version contains any fixes which help you.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors
I'm glad you posted
I'm having the same problems with the current version of Drupal after my 6.24->7.12. I have since upgraded to 7.14. I'm getting everything to work as is and finally needed to add content when I realized I can't add a basic 'content' type. I get the exact same errors, but on line 654 of file.inc.
Did you ever work out the problem without creating a new content type? I have a month into theming and getting everything to work in this version. I can't do the 6->7 upgrade again or rebuild the content type.
I'm interested to know how it worked out for you, lionheart8.
Hi probably I had too many
Hi
probably I had too many modules, whose upgrade was not that easy. After trying upgrading & asking in the forums for solutions to different module issues, i decided to simply give this up as I was not getting some critical answers, at least when I needed them. I needed for example to have my old images/gallery, the meta stuff (nodewords module), etc upgraded. There were serious problems upgrading that content, although there are supposed to be functioning means.
I was also heavily using apart from the D6 image module (which is supposed to have an upgrade path to the D7 solution, this did not quite work for me), the node image module, for which there's no D7 version, etc.
I took a difficult decision to simply re-do the site from scratch in Drupal 7 & simply copied & pasted to content from the D6 to D7 site. It took lots of time & work, but it was the best way in my case, with a fresh installation. It ha a good bit of content after about 3 years old & I decided to discard some. I had no choice, as I had to have a functioning site & I had already given up D6.
This is the result => OrbitUganda with D7 modules, third party, etc, which are much better.
It seems one's needs to be a coder to be able to deal with some errors that come up, especially if you use certainly modules in D6, that either no longer exist in D7 format or that cannot be upgraded smoothly. The upgrade of the core itself, with third party modules disabled was smooth.
I hope you find an appropriate solution.
Regards
Interesting site. I was
Interesting site. I was reading some of the proverbs!
It is usually best to create a new site in D7. I have just upgraded a site, but I removed as much as possible of the non-core core stuff first. Just left CCK, Views, Nodewords, and a few other contrib modules. Even so, I am not sure it would not have been easier to build from scratch. This contrib upgrade nightmare is a bad problem for Drupal, let us hope the Drupal7>8 upgrade path is easier.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors
Wow.
Now I'm sad. I really can't recreate all of the data.
As this point, I think I'll have to lose my images and hopefully get the internationalization working (the only thing left with errors).
I was thinking about using removing the broken field and adding it back in fresh, which seems to work. Then using feeds to replace my images from our existing D6 site, but even Feeds imports looks to have show-stoppers now according to the issues pages. I have Feeds import working in a fresh D7 install mobile site, but even that took over 2 weeks of debugging. But I digress.
Thanks for your follow up. If I end up fixing this, I'll report back :)
Did you use imceimage in D6?
I'm curious if you used imceimage or something else in Drupal 6?
Our site did and I converted to filefield prior to upgrading to D7. It appears that imceimage_height/width/alt are being sent for the first $fid arg and causing the error.