[support] support Digest, Vol 113, Issue 20

Roger arelem at bigpond.com
Thu May 10 23:14:08 UTC 2012


On 11/05/12 08:30, support-request at drupal.org wrote:
> Send support mailing list submissions to
> 	support at drupal.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.drupal.org/mailman/listinfo/support
> or, via email, send a message with subject or body 'help' to
> 	support-request at drupal.org
>
> You can reach the person managing the list at
> 	support-owner at drupal.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of support digest..."
>
>
> Today's Topics:
>
>     1. Re: Problem with Organic groups (Earnie Boyd)
>     2. Views Showing Wrong Page (Swapnil Bhartiya)
>     3. Upgrading from Drupal 6 to Drupal 7 (Earnie Boyd)
>     4. Re: Upgrading from Drupal 6 to Drupal 7 (Earnie Boyd)
>     5.  PHPMyAdmin access error (Anthony)
>     6. Re: PHPMyAdmin access error (Steve)
>     7. Re: PHPMyAdmin access error (Gerald Klein)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 10 May 2012 08:45:39 -0400
> From: Earnie Boyd<earnie at users.sourceforge.net>
> Subject: Re: [support] Problem with Organic groups
> To: support at drupal.org
> Message-ID:
> 	<CA+sc5mmYzA5FPjf-pDQhHB6vvUvr5PN6H-r8Qp2NUs4Askny+Q at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Thu, May 10, 2012 at 6:59 AM, Roger<arelem at bigpond.com>  wrote:
>> using Drupal 7.14 all modules updated I had the problem reported last
>> week with organic groups trashing ?my site.
>> Following advice I upgraded OG to 7.x-2.x-dev which may cure some ills
>> however it needs to run Migrate.
>> Migrate of Upgrade OG membership - 7.2 Re-populate group ID and group
>> entity, deprecating the OG group entity Executed but failed
>>
>> An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information
>> follows. Path: /d7x/batch?render=overlay&id=48&op=do StatusText: Service
>> unavailable (with message) ResponseText: EntityMalformedException:
>> Missing bundle property on entity of type node. in entity_extract_ids()
>> (line 7539 of /var/www/html/d7x/includes/common.inc).
>>
> So looking at http://api.drupal.org/api/drupal/includes%21common.inc/function/entity_extract_ids/7
> we can see the reason for this error.  And looking at
> http://api.drupal.org/api/drupal/includes%21common.inc/function/entity_get_info/7
> I can determine that something has implemented a hook_entity_info
> without the required 'bundle' array element.  There isn't enough here
> to say to which module the hook implementation belongs.
>
>> There are similar error reports on google,not specifically for OG, ?but
>> no resolution.
>>
>> Has anyone had similar problem and how was it fixed please.
>>
> No, it is module specific so you need to find the broken module.
>
>> I have reported it ?but as my report was only the third ?and the other 2
>> said the problem was fixed I see no way of getting assistance.
>> Og cannot be removed without irreversible damage to the database.
>> What should be done please.
> It sounds as if you've already issued at drupal.org/project/issues/og.
>   I also guess from your plea that you've upgraded directly to a live
> site without testing first.  Did you do a backup so you can restore?
>
I am somewhat fortunate that the live site isn't live yet.
I first successfully tested on a home installation but did not find the 
mess that og causes until I installed the og module on the "soon to be" 
live site.
I am also fortunate that I have not put the og dev module into the stb 
live environment and have switched all the og modules and their 
dependencies off in that setup.

I'm about to test the backup this week end on my home setup.
Problem is, I need to implement a rather awkward/convoluted edit, 
review, publish system which Maestro and workbench do not do well. My 
only option was og.
  How do I find the broken module. Would devel help to isolate where and 
how? I'm hopeless at PHP so am doubtful that I would know what to look for.



More information about the support mailing list