Download & Extend
Drupal SEO Friend (Tools & Reports) » Issues

Illegal offset type in ../sites/all/modules/seo_friend/seo_friend.admin.inc on line 485

Posted by Starminder on January 25, 2010 at 5:22pm
Project:Drupal SEO Friend (Tools & Reports)
Version:6.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Kristen Pol
Status:closed (fixed)

Issue Summary

Type: php
Illegal offset type in /usr/home/hoslo/public_html/sites/all/modules/seo_friend/seo_friend.admin.inc on line 485.
Backtrace: seo_friend_nodewords_report(a:0:{})[seo_friend.admin.inc:388] <=seo_friend_reports(a:0:{})[?:?] <=call_user_func_array(...)[menu.inc:348] <=menu_execute_active_handler(a:0:{})[index.php:18] <=index.php

Login or register to post comments

Comments

#1

Posted by Kristen Pol on January 26, 2010 at 5:26pm

Hmmm... is this happening for all reports or for a certain report or ???

Kristen

#2

Posted by Kristen Pol on February 5, 2010 at 2:27am
Status:active» postponed (maintainer needs more info)

#3

Posted by Starminder on February 19, 2010 at 5:03pm
Status:postponed (maintainer needs more info)» needs work

This occurs after running the meta tag node report only - thanks!

#4

Posted by Kristen Pol on February 20, 2010 at 12:53am

What nodewords version? There is a new beta6 version if you want to try that though I don't know if it will help with that problem.

Kristen

#5

Posted by Kristen Pol on February 20, 2010 at 12:55am
Status:needs work» postponed (maintainer needs more info)

#6

Posted by Starminder on February 22, 2010 at 8:15pm
Status:postponed (maintainer needs more info)» active

Using latest nodewords dev dated Feb 20. Confirmed problem still exists.

#7

Posted by comparellc on February 24, 2010 at 10:41pm

Subscribing to thread. I also have the same problem. and only on meta tag report.

#8

Posted by Kristen Pol on February 24, 2010 at 11:24pm

I just upgraded to latest nodewords dev and am using latest seo_friend dev (pretty similar to beta6) and still don't see the error.

If one of you is willing to do a dump and zip of your database and send it to me directly, I can install it locally and see if I can reproduce.

Oh, and just to be sure, after you updated nodewords, did you run update.php?

Thanks,
Kristen

#9

Posted by Kristen Pol on February 24, 2010 at 11:31pm

I checked in one very minor change which may help that error go away. But, since I can't reproduce the error, I'll need one of you to try it once the new dev version is created with the drupal cron.

Thanks,
Kristen

#10

Posted by Kristen Pol on February 27, 2010 at 4:49am
Assigned to:Anonymous» Kristen Pol

#11

Posted by comparellc on February 27, 2010 at 10:15am

Are the dev versions very stable? The site I am working on cannot afford to lose stability, as we have a very quickly growing user base.

#12

Posted by Kristen Pol on February 27, 2010 at 4:11pm

Well, the dev version works for me, but I'm not sure that constitutes as "stable".

You may know all of the following info, but putting it here in case it is useful for someone...

It's always best to try out any new version of any module you are going to use on a staging/dev site first with a copy of your live data to test out. The model I typically have use:

* dev site (where development is active)
* staging site (copy new features for client to test)
* live site

Once things are approved on staging, they go live. And, when rolling out to live, I:

* put the live site in maintenance mode
* create a copy of the database
* create a zip of all code
* copy over code changes
* make configuration changes via browser
* test
* if something goes wrong that can't be fixed quickly, revert to copies I just made
* otherwise, come out of maintenance mode

Kristen

#13

Posted by Starminder on March 5, 2010 at 4:14pm

Still getting error with latest dev - let me know what to send you so I can help, thanks!

#14

Posted by Kristen Pol on March 5, 2010 at 4:24pm

If you are able to zip up a dump of your database and email it too me directly, that would be great. Also, please verify the nodewords version one more time and I'll make sure I have everything the same.

Oh, and what version of php are you running?

Thanks,
Kristen

#15

Posted by Kristen Pol on March 11, 2010 at 5:28pm

If you are worried about sharing your database, you could:

* create a test site with same code base
* import your database there
* delete all users (except uid=1)
* delete any content you don't want shared
* dump/zip database and send it to me

Kristen

#16

Posted by Kristen Pol on March 11, 2010 at 5:29pm
Status:active» postponed (maintainer needs more info)

#17

Posted by Gerben Zaagsma on April 4, 2010 at 12:53pm

subscribing

#18

Posted by Kristen Pol on April 4, 2010 at 3:28pm

Gerben,

I've been unable to reproduce this bug and am hoping to get a dump of someone's database (ideally along with a zip of their modules directory) so I can try to reproduce and, thus, fix.

If you are willing to do that, please see comments #14 & #15. You can email me it directly if you prefer. If you contact me via drupal, I'll send you an email address to use.

I really want to fix this bug, but need someone's help.

Thanks,
Kristen

#19

Posted by aiphes on April 13, 2010 at 7:43am

i've the same issue ...this is the error content for me :

Type php
Date 12 avr. 2010 - 16:27
Utilisateur admin
Emplacement http://www.xxxxxxxxxxxx/site/admin/reports/seo/nodewords
Référent http://www.xxxxxxxx/site/admin/reports/seo/nodewords_bypath
Message Illegal offset type dans /xxx/xxxx/www/site/sites/all/modules/seo_friend/seo_friend.admin.inc à la ligne 485.
Importance erreur
Nom d'hôte xx.xxx.xx

my versions of differents modules :
SEO Friend 6.x-1.0-beta6
Nodewords 6.x-1.x-dev (2010-févr.-23)

#20

Posted by Kristen Pol on April 13, 2010 at 3:46pm

What do you have your php error reporting set to? Maybe I need to report more errors and it will show up?

Thanks,
Kristen

#21

Posted by aiphes on April 14, 2010 at 1:38pm

i dont know what are the setting for php error reporting because my website is on OVH...so this what the phpinfo tell to me:

display_errors STDOUT STDOUT
display_startup_errors Off Off
track_errors Off Off
xmlrpc_error_number 0 0
xmlrpc_errors Off Off
error_append_string no value no value
error_log no value no value
error_prepend_string no value no value
error_reporting 6135 6135
log_errors Off Off
log_errors_max_len 1024 1024

#22

Posted by Kristen Pol on April 14, 2010 at 3:49pm

Those are my settings as well. What version of php are you running?

Are you willing to send a database dump? So far, several people have this problem, but no one has sent me one. I have the best chance of reproducing the error with a copy of a database that is showing this error.

Thanks,
Kristen

#23

Posted by aiphes on April 15, 2010 at 8:20am

my php version : PHP Version 5.2.12
it(s will be hard to send you a DB dump....i'll see what i can do..

#24

Posted by locomo on April 27, 2010 at 6:55am

subscribe

#25

Posted by Kristen Pol on April 27, 2010 at 4:11pm

locomo - please let me know which version of seo_friend you are using, and what line number the error is for you.

Thanks,
Kristen

#26

Posted by locomo on April 27, 2010 at 4:22pm

sorry for the unhelpful report.. here's my backtrace.. i can try to get you a db dump later today if that would help

i'm using the latest dev release of nodewords and stuff is changing constantly in that module...

Location http://xxxxx.net/admin/reports/seo/nodewords
Referrer http://xxxxx.net/admin/reports/seo/main
Message Type: php
Illegal offset type in /home/xxxxx/public_html/drupal/sites/all/modules/seo_friend/seo_friend.admin.inc on line 522.
Backtrace:
seo_friend_nodewords_report(a:0:{})[seo_friend.admin.inc:422];
.seo_friend_reports(a:0:{})[?:?];
..call_user_func_array(a:2:{i:0;s:18:"seo_friend_reports";i:1;a:0:{}})[menu.inc:348];
...menu_execute_active_handler(a:0:{})[index.php:18];
....index.php

#27

Posted by Kristen Pol on April 27, 2010 at 4:48pm

I would LOVE LOVE LOVE a db dump. I've been asking for someone to give me one for awhile but nothing yet. I've found the easiest way to reproduce these kinds of errors is to recreate the site locally as best as possible. I would really like to squash this bug.

Thanks!
Kristen

#28

Posted by comparellc on April 28, 2010 at 12:17am

The thing is, a db dump is tough to give to someone when the content is copyrighted..:(

locomo, if you can send kepol the db dump, im sure we could get a solution in the works..

#29

Posted by Kristen Pol on April 28, 2010 at 12:49am

Good point. One possibility would be:

1) dump database

2) install on test site

3) delete all nodes

4) use devel module to generate new nodes

5) verify issue still exists

6) if so, dump database

7) send version from #6

May not be able to recreate error without the same nodes, but worth a shot if no one can send me a "real" database.

Btw, you can remove all users except uid=1. And, I don't need the password for uid=1 because I can change it.

Cheers,
Kristen

#30

Posted by locomo on April 28, 2010 at 1:52am

@kepol - i just pinged you for your contact info .. i have a db for you

#31

Posted by Kristen Pol on April 28, 2010 at 5:07am
Status:postponed (maintainer needs more info)» fixed

Thanks locomo!!!

I've just checked in what I'm hoping with be the fix... yeah! It will be in the next dev version that is created during the next drupal cron run.

Please test when it's there and report back 'yeah' or 'neah' (sp?).

Thanks,
Kristen

#32

Posted by locomo on April 28, 2010 at 6:42pm

tested - no errors

woot woot!

thanks Kristen

#33

Posted by Kristen Pol on April 28, 2010 at 6:45pm
Status:fixed» closed (fixed)

Yippee skippee!!

Thanks for helping out locomo! I'll delete your db dump from my computer.

I'm going to roll out a new beta version later today but meanwhile, I'll mark this as closed.

Cheers,
Kristen