Has anyone else had issues with MAMP and the taxonomy module (i.e. core)?
I had noted this before and was checking this as i have some database gremlins in an upgrade from 4.6 -> 5.1 i am trying to resolve.
When i create terms in a category (on a new install) running on MAMP and OS X (creating categories runs smoothly) i get the following errors
<ul>
<li>warning: Illegal offset type in isset or empty in /Applications/MAMP/htdocs/test-install/modules/taxonomy/taxonomy.module on line 1150.</li>
<li>warning: Illegal offset type in /Applications/MAMP/htdocs/test-install/modules/taxonomy/taxonomy.module on line 1151.</li>
<li>warning: Illegal offset type in /Applications/MAMP/htdocs/test-install/modules/taxonomy/taxonomy.module on line 1154.</li>
</ul>
where test-install is a new install of drupal...
Anyone else noted this, or had similar issues??
I had ignored it yet when i exported a dbase and imported it into a new remote install i get the errors as well when trying to create categories. Creating nodes and selecting taxonomy terms leads to no errors.
any thoughts would be appreciated.
Whilst a search came up with nothing, if anyone else has had similar experiences i might log an issue
thx
c.
[FYI this happens with a fresh install of MAMP as well]
Comments
I suspect the upgrade
Hi avolve -
I'm running the current version of MAMP on OS X (10.4 with all updates), and have a clean install of Drupal 5.1 running on it. There's some special configuration in mine that might not be in yours (I've relocated my htdocs folder into a location I commonly access and backup, I've added virtual hosts to my httpd.conf file, and I added host names to my /etc/hosts file so that I can access my sites like this: site1.dev:8888 ... site2.dev:8888 ... etc).
Anyhow, I tested creating a new taxonomy category, and then added some vocabulary to it, and it all went through without any errors. So I'm thinking it has to be something related to your upgrade from 4.6 to 5.1. Unfortunately I don't personally know how to help you with that, but hopefully someone will. One thing you can test... since you have MAMP and Drupal 5 is so easy to install now ;-) you can quickly setup a clean test site to see if the problem is reproducible, or if it's limited to your upgraded version. If it happens in the fresh install, then you'd have reason to suspect something in your local system causing the issue - otherwise the problem lies in your upgraded version of Drupal.
Hopefully you did make a backup of your 4.6 copy before upgrading. Greater Drupal minds might have a better idea, but I think you might try reverting to that, and upgrading through 4.7 first, then to 5. Maybe do a little "house cleaning" first before upgrading as well (e.g. go into the database and remove gunk from old modules you've "uninstalled" - which aren't actually uninstalled in versions prior to 5). I don't know what to advise you to look for, but a search for "uninstaller" or "uninstalling modules" should lead you to the advice on what to look for and in which tables.
Good luck.
-- Dave
Had the same issue after
Had the same issue after upgrading a 4.7 site to 5 - i could not figure out why categories were not working on my local dev mamp installation and works fine on a live server.
One thing I thought about
One thing I thought about today was that it "might" be related to your MySQL version. Was the Drupal 4.6 site something that was running on a live server, which you downloaded to do your local upgrade testing before applying it to the live version? If so, perhaps your live server has an older version of MySQL running, which I believe could affect your database itself in some ways. When you then used MAMP with a newer version of MySQL to do your Drupal upgrade, maybe that could have introduced these problems.
Anyhow, could be worth checking into. If you need to find out what version of MySQL you have on your live server, a failsafe way to get it is with a phpinfo() file. Just upload that and it should tell you. Compare that to the version of MySQL in MAMP. If this ends up being the case, there might be some ways to process/prepare your database ahead of time before dropping it into a new version of MySQL.
-- Dave
thanks...
thanks for sharing your thoughts.
It is not just related to my 4.6 -> 5.1 upgrade (i did go through 4.7).
I had noted this before that upgrade and tested it (again to make sure) this morning on a clean install with new dbase.
The error message above included 'test-install' - then name i gave this. I have no idea why this is happening...
[FYI i have gone through the upgraded dbase and cleaned it up]
thx
c.
avolve designs | ethical by design
to add to this...
the site is now live and i tried to set up user blogs with free tagging and got the following errors on a test blog
warning: Illegal offset type in site/drupal/modules/taxonomy/taxonomy.module on line 1154.
i have no idea why - the site is http://www.sandon-point.org.au
I reinstalled the taxonomy module to no avail...
anyone have any ideas at all??
[EDITED TO ADD]
this (i assume) is also affecting pathauto. i can get it to generate working alias' for already posted blogs (i deleted the free tagging), though it does not generate for any new posts (including blogs).
i assume i have to go back the database and dig around - it must be something in there (what else could it be?)
i really am stuck on this one!
avolve designs | ethical by design
this is a pathauto problem
I have MAMP and was getting the same error. Fixed when I upgraded my version of pathauto.
See http://drupal.org/node/92900
and http://drupal.org/node/112084
John
thankyou for this
Thank you for letting me know - it appears this solved the issue. Only two more (minor) bugs with the theme to resolve...
cheers
.c
avolve designs | ethical by design