Postponed (maintainer needs more info)
Project:
Organic Groups Blueprints
Version:
5.x-1.0-alpha1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
22 Mar 2008 at 05:19 UTC
Updated:
9 May 2008 at 05:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
najibx commentedohh ...I didn't select group in "Group home page node types: " in OG setting.
Even so ...when selected, I am getting this error and I don't think panel is taking over my OG home.
as well as duplicate error !
* warning: array_filter() [function.array-filter]: The first argument should be an array in /home/igolfcommy/public_html/sites/all/modules/og/og.module on line 2503.
* warning: array_fill() [function.array-fill]: Number of elements must be positive in /home/igolfcommy/public_html/sites/all/modules/og/og.module on line 2503.
* warning: implode() [function.implode]: Bad arguments. in /home/igolfcommy/public_html/sites/all/modules/og/og.module on line 2504.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') AND ogu.nid = 13 AND ogu.is_active = 1 AND u.status = 1 ORDER BY ogu.created D' at line 1 query: SELECT DISTINCT(u.uid), u.* FROM og_uid ogu INNER JOIN users u ON ogu.uid = u.uid WHERE ogu.is_admin IN () AND ogu.nid = 13 AND ogu.is_active = 1 AND u.status = 1 ORDER BY ogu.created DESC LIMIT 0, 10 in /home/igolfcommy/public_html/includes/database.mysql.inc on line 172.
------------
Duplicate error
# user warning: Duplicate entry '194-194' for key 1 query: INSERT INTO node (nid, vid, title, type, uid, status, created, changed, comment, promote, sticky) VALUES (194, 194, 'Kaki main', 'og', 1, 1, 1206163908, 1206163908, 0, 0, 0) in /home/igolfcommy/public_html/includes/database.mysql.inc on line 172.
# user warning: Duplicate entry '194' for key 1 query: INSERT INTO node_revisions (nid, vid, title, body, teaser, timestamp, uid, format, log) VALUES (194, 194, 'Kaki main', '', '', 1206163908, 1, 0, '') in /home/igolfcommy/public_html/includes/database.mysql.inc on line 172.
# user warning: Duplicate entry '194' for key 1 query: INSERT INTO xmlsitemap_node (nid, pid, last_changed, priority_override) SELECT 194, ua.pid, 1206163908, NULL FROM node n LEFT JOIN url_alias ua ON ua.src = CONCAT('node/', 194) LIMIT 1 in /home/igolfcommy/public_html/includes/database.mysql.inc on line 172.
Comment #2
sdboyer commentedYour initial question - one possible cause for the panel you've created to not take over the group home page is because it's unpublished. The way that og_panels is set up, if you have an og_panels page set to act as the group homepage but it's unpublished, then the og_panels page simply won't show up and you'll be looking at the node as it's normally rendered. For the pre-configured panel you designed in og_collections to automatically show up as the group home page for a new group you create, you've gotta make sure it's both 'Enabled' (which means it WILL be added to new groups of that type) and 'Published' (because of the reason I gave before - if an og_panels page is set as the group homepage but unpublished, you don't see it).
Based on the SQL errors that you've pasted in here, it's tough for me to say exactly where the error you're encountering is coming from. Are these errors occurring when you create a new group, or when you're doing something in the og_collections administrative menu?
Line 2503 of og.module is some of the new code that moshe put in for og_panels, so I don't know where on the continuum of his work vs. my work this issue falls. I'm going to switch this issue over to that queue and see if he has any ideas; it's possible that the changes he's made necessitate changes to og_collections that I have yet to make.
Comment #3
najibx commentedThank you for you feedback.
I checked/enabled Home Page, Enabled and Publish in "Collections". See attached. This panel is listed in "Pre-Configured Panels" and have insert some content.
Still it does not taking over.
The first error is all in OG-related page except when there is no content in the Group.
Second error gone after I only select 'Group" in OG Homepage setting.
BTW, I have the og module dated March 22 Head
Comment #4
najibx commentedTaken care the duplicate errors by synchronizing my sequence, node and node_revision table. Somehow it got messed up by unknown reasons ...
With today HEAD version (March 23), i am still having errors below. From the SQL statement, it looks like it's looking for "ogu" table ...which I cannot see one in my database?
Comment #5
sdboyer commentedHi najibx - I've posted some small bug fixes as the ALPHA2 version of og_collections. Try upgrading to the most recent release and see if that helps your problem, or at least changes the error messages. I suspect they may have been the source of your difficulties.
Comment #6
sdboyer commentedHi najibx - I've posted some small bug fixes as the ALPHA2 version of og_collections. Try upgrading to the most recent release and see if that helps your problem, or at least changes the error messages. I suspect they may have been the source of your difficulties.
Comment #7
sdboyer commentedComment #8
najibx commentedThank you for kind attention.
Upgrade to 5.x-1.0-alpha2.
The problem is still there. Not taking over page and errors.
would the cause be og.module ?
Comment #9
sdboyer commentedPossible, but still not 100%. What other modules do you have installed?
Comment #10
najibx commentedThe page is not taking over because the earlier Groups was not in the "og_panels" table and have own panel in "panel_display"
It's weird that eventhough I edit/save the previous group, it does being added/updated automatically. Only new group created will have their group overtaken by panel.
Furthermore, whenever, I change panel content or layout, it does not taken effect. Only new groups will have this new layout/content.
Normally, in panels2, it's take effect immediately with panel cache is disable.
But errors msg still persist !
Comment #11
sdboyer commentedI still would like to know what other modules you have installed.
I'm not quite clear on what you're saying - prior to using the og_panels & og_collections modules, you were using panels_pages to override the group homepages? If that's the case, you'll need to delete any panels_pages that are being used for those old groups.
This is the way og_collections is supposed to work. Once the groups have been created and the pcpanels have been instantiated as og_panels for that group, the connection to the pcpanel is 'severed.' Now, I am planning to develop a system where it will be possible to update the og_panels that have been instantiated by og_collections - either individually at the discretion of the group admin, or en masse at the discretion of the site admin - but that capacity does not yet exist, and may not for as much as another couple weeks.
I do have one thing I need to check, but I'm going to ping-pong this back over to the og_panels queue if it doesn't turn out to be related.
Comment #12
najibx commentedIn general there are too many modules to list down here. As far as OG related, I have tried to disable many of them ..now left with OG, og_collection, og_forum, og_calendar, og_panels
also earlier i used node type as "og" now ... node type as "groups". Until now I am still not so clear on these .either one works?
Ok, with the way og_collections is working, it all make senses. Some groups were created before I have OG collections/panel. When I am trying to update these groups, since you explain it's not being updated ... old groups does not have their page overridden by og_panel.
You effort to create that system would be very useful.
TQ
Comment #13
najibx commentedThose errors are NOW gone. http://drupal.org/node/239817
Comment #14
Anonymous (not verified) commentedI'm having the exact same issue, drupal5.7, og6.1, panels2beta3, views1.6.
I do have a lot of other modules installed, but I did try uninstalling every module except og, og_panels, panels, views, and og_collections, and I still get the same error messages and problems.
Error msg only appears on og_collections/collectioncfg:
warning: mysql_num_fields(): supplied argument is not a valid MySQL result resource in /Applications/MAMP/htdocs/anvill/sites/all/modules/og_collections/og_collections.module on line 170.
The other issue is that old groups' homepages are not replaced by panel, though new groups are.
I haven't tried on a clean install yet, because of the length of time to set up content types and groups.
I've tried using the posted dev version, but I get even more error msgs, so I didn't pursue that.
Thanks for all your work, I'm looking forward to integrating this module into my sites!
Comment #15
sdboyer commentedI'm still not entirely sure what could be causing this, but I can say this - I'm just finishing a pretty much complete rewrite of the og_collections code, including the discontinuation of the module using this name. You'll be able to port your data over to the new version (it'll be called og_blueprints), but hopefully it'll take care of this issue. If not, we'll track it down then.
Unlike some folks, I ACTUALLY use the -dev version for devving :)
Comment #16
sdboyer commentedPlease let me know if this error persists once you've upgraded to Blueprints alpha1. I'm still not quite sure what could be causing it, but I've reworked pretty much everything about the module, so there's a decent chance it got fixed along the way (if it had anything to do with Collections/Blueprints in the first place)
Comment #17
Hetta commenteda similar problem elsewhere turned out to just require a manual update of the sequence table: check that the largest values there correspond to the largest values in the related tables' keys (nid, tid, whatever).
http://drupal.org/node/255238#comment-837347
Comment #18
sdboyer commentedYes, najibx already updated in sequences table, as he indicated in #4. The duplicate key issue is incidental and not related to the root issue at hand, which hinges on one of the new SQL queries in og.module written to support og_panels. The only potentially relevant sequences for which the source of the problem could actually lie in this module are {panels_display}_did, {og_bundle}_bid, and {og_blueprint}_bid.