Can neither create nor delete (some) default content types

I am not able to reproduce this. How did you install Atrium. Did you do a from-scratch install of the -dev version, or did you have a previous version installed?

Not sure what "tasks" you are talking about yet since we haven't integrated tasks. Maybe try creating a Discussion Section and then create a discussion post within the section. I'm not having any trouble creating events within a calendar section.

Reopened issue, error is the same:
(slight difference is the version of Open Atrium (the version I am using is: 7.x-2-beta4, previously was this issue was for: 7.x-2-dev)

Details:

• I can not save (as draft or published) a Discussion posts: node/add/oa-discussion-post?oa_section_ref=86
• Error received:

EntityMetadataWrapperException: Invalid data value given. Be sure it matches the required data type and format. in EntityDrupalWrapper->set() (line 744 of /var/www/openatrium.drupal.dev/www/profiles/openatrium/modules/contrib/entity/includes/entity.wrapper.inc).

Installation process of OA - brief info: I'm using Vagrant, cloning repo of tar.gz archive from d.o OA project page, manual install from this point. Fully documented here: https://gist.github.com/kae76/6903482

Please if any further information is required then I will be more than happy to give more info, I frequent the #open_atrium IRC channel (with the same nick)

Many thanks
Karen

You'll need to give me the exact steps taken to reproduce this as I still cannot reproduce it. Also, you need to test on the latest -dev versions since dozens of bugs have already been fixed since the beta4 version.

I'm now testing on my dev server rather than local, and I get the same error.

• Logged in as UID 1
• In top nav menu drop down "subscribe sections": Selected: create a new Space, which is private. populated the mandatory fields. saved.
• In top nav menu drop down "Sections": Selected: create new Section, Section type: Discussion Section. populated the mandatory fields. saved.
• in Section top nav selected + "create discussion post" populated the mandatory fields. saved.
• at this point I get the error:

EntityMetadataWrapperException: Invalid data value given. Be sure it matches the required data type and format. in EntityDrupalWrapper->set() (line 744 of /var/www/openatrium.drupal.dev/www/profiles/openatrium/modules/contrib/entity/includes/entity.wrapper.inc).

I have not been able to update to the dev version of this project on my vagrant repo/local build, I understand if this has been fixed, that's great; but I haven't seen anything in the issue queue to suggest this has been a known and fixed issue.

I'm coming to the end of my working day (UK based) I will attempt to update to the latest dev first thing tomorrow, and give you feedback on the results.

thanks for the reply.

Trying to dl the latest dev version as requested in comment #3: https://drupal.org/node/2107919#comment-7949521

I'm getting a not found error, so I am blocked from testing this further.

Not Found

The requested URL /files/projects/openatrium-7.x-2.x-dev-core.tar.gz was not found on this server.

Apache Server at ftp.drupal.org Port 80

Hi Hazit, Thanks for the heads up,
for your ref I asked a few other people to test the same link different machines, browsers, it does seem to be specifically this url.

I've post #7 here: https://drupal.org/node/2107827#comment-7952141

Hazit might be of some help: I have managed to get a dev version of OA as documented here: https://drupal.org/node/2107827#comment-7957061

I still receive the error following the same steps I out lined in #4 https://drupal.org/comment/reply/2107919/7952159#comment-7949611

Hazit you mentioned in #6 https://drupal.org/comment/reply/2107919/7952159#comment-7951289
Group Audience field being an issue, I have not managed to test this yet.

I will have a look though.

new clean dev build. (oct 12) -parked my site-

created space, section (discussion), added discussion. saved no problem.

added new users roles, set some perms,

created group added users to group.

made an edit (as user1) to discussion post received the same error as https://drupal.org/node/2107919#comment-7949611

This seems to be happening for me with section pages. I haven't done extensive configs with this installation. If it is with the groups audience field as a previous poster mentioned (and yes, when I remove it, I can save info -- but then it no longer appears as it should -- like on the calendar), I haven't done anything in that field in the pre-config content types other than adding new spaces and sections (that it pulls from).

Does this post help anyone at OA who's looking into this: https://drupal.org/node/1925412#comment-7900055? Or this: https://drupal.org/node/1673220#comment-7899987?

I'm using this version of OA: openatrium-7.x-2.0-beta4+11-dev. I see there's a full release that just got posted (7.x-2.0 on 10/23). Any idea if this might have been corrected/addressed in that release? Trying to get a site live soon and hesitate to upgrade to a new OA release right now unless this has been fixed in it (vs. hoping a quick patch to fix this might be forthcoming).

Hundreds of issues have been fixed since beta4. I can only help you when using the latest version of OA2. We have dozens of sites using OA2 and none of them have any trouble creating or deleting nodes on fresh installs. If you still have the problem then my only suggestion is doing a clean install.

I can try a new install, but I've done a lot of customization (basically, adding modules and creating spaces and sections, that until the past couple days introduced no problems). My concern is that if in between every release when there are bug fixes, and the only solution to errors and bugs that come up is to try a "clean install" it's going to be hard to use this distribution. If every time I experience a problem I have to abandon an existing site and start from scratch, I'm not sure that's feasible. Plus, if a clean install produces no errors (as did the clean install of the beta4+11 that I used originally -- it did not produce these errors and worked fine for the 2 weeks I used it and customized it), and then I use, customize, add content to the site and install additional modules that I need and then I get the error again, what then? If it's a problem with a module I've added, what's to say it won't happen again? I can't create a new site from a clean install every time. Had this been a problem from the start, I could see that a clean install of the latest release would be the first option. But this install (when it was clean and even after adding to it) had no issues, either.

So, I just tried a fresh install of the 7.x-2 full release and now I get an error during install.

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://workspace.earthcube.org/install.php?profile=openatrium&locale=en&id=1&op=do StatusText: OK ResponseText: Parse error: syntax error, unexpected $end in /home/earthcub/public_html/example.com/profiles/openatrium/modules/contrib/fieldable_panels_panes/fieldable_panels_panes.module on line 85

You better open a new issue for that error.

Sorry to be a pain, but I can only support "clean" Open Atrium installs. Once you start doing your own changing and customizations then you are in the territory of asking for general Drupal guidance. I can't help with issues that cannot be reproduced. Drupal lets you do all sorts of things the might or might not work smoothly with any distribution, not just Drupal. It is a very complex collections of modules being glued together that works well for the use-cases that it is intended. Working beyond that will take more detailed help and debugging from the community.

I've posted several times about module updates already. When using a Drupal distribution you should NOT be doing your own module updates. You need to wait for the distribution to be updated. If you update modules on your own then you are on your own for help as the module updates might be missing important patches or otherwise have compatibility problems with other modules.

In #16: You must have a corrupted installation download as that error is basically telling you that the code in the fieldable_panels_pane module is ending abruptly and it's certainly not an error I have seen on any of dozens of different OA2 installs.

#18: You need to restore the Group Audience field. That is a core field from Organic Groups and removing that will completely break Open Atrium with your custom content types. The Group Audience field is from Organic Groups and if that doesn't work with your content type then it's more of an OG issue and not an Open Atrium issue.

Sorry that this can be frustrating, but there is a whole community of modules involved here so it's going to be important to take specific issues to specific modules. We can't have this be the issue queue for any Drupal module used in Atrium. And we can only really help with issues that can be reproduced on a clean OA2 site. Otherwise it's just a debugging nightmare.

In the future I hope we can improve how Drupal handles Distribution Updates vs just Module Updates.

hazit and mpotter -

Thanks for your posts! My silence since my last post was due only to trying to fix the site so a small portion of it could be shown to others today. And by fix, I mean spending 3 hours trying to fix it and then giving up (updating og, clearing caches, checking values in the database, etc.). From what I found, it looks like it might be an error that appears to happen with entity API periodically (saw the same error mentioned over 6 months ago in another post that was not OA related) and then the entity API forums seem to point to other module developers as writing something not quite compatible with their module.

The failed clean install was a corrupted file -- found that about 5 minutes after my post -- but again, couldn't take time to update that.

I did break down and build the whole site from scratch again -- using the latest release. :( I was fortunate in that I didn't have a lot of content -- just had the structure/pieces set up to accept a bunch of content, so I had to recreate/rebuild the skeleton from scratch. I had started the site near the end of Sept/beginning of Oct and had done one OA upgrade in the meantime. Though I know mixing distributions and module updates is not always the best idea, I ran into enough errors with the first OA distributions that impeded my progress -- so I decided to try some (it was that or move to Drupal Commons because we're on a tight schedule and that's my next best choice). Those fixes didn't seem to cause the above error (at least the issue didn't manifest till at least a week after the last OA module update/tweak/patch). And the fixes did make things work better that had been broken. I also installed other modules and it's possible one of those caused/contributed to the problem (I did install a few just before the issue surfaced). And, of course, I may have changed a setting that triggered this (saw some talk about unlimited vs. 1 as a choice in the group audience field settings possibly being related to the error). My concern is that I just can't rebuild the site from scratch every time I encounter an error and I can't keep the distribution free of outside modules. While OA has about 80% of the features we need/want, there's the other 20% that I need to address. And, while it's a distribution, there's always talk about how it's Drupal at its core and that means you can extend its functionality with additional modules. Just like any other Drupal site, any module can cause problems -- that could be an triggered by something in OA or in the additional module.

But it was tough seeing that others using OA (even if it's not a full release version) have the same errors, but the only real suggestion was to wipe the site and start fresh. I wish I could say my OA site would exist in a bubble and never be tainted/adulterated by any other modules, or that I could ignore errors that come up that make a part of the site non-functional (and wait for the next official OA upgrade), but it's just not possible for me. I had hoped the forums would be a place to get suggestions and other opinions on things to look for or try. Especially when it was apparent my installation, with its updates and patches and errors, wasn't the only one seeing this -- since others are reporting the same error using an OA distribution.

I just wanted to say that I appreciate the quick responses, but I'm hoping that the go-to answer for future issues that appear to be part of/related to OA (and may not be -- but at least start off looking that way) won't be "you need to do a clean install" because your OA isn't the latest version. So far, with the maybe 10 or so other sites I've built in Drupal, I haven't had to fully abandon any of them because of any error. At some point, the community, the developers and updates and patches have always come through with a fix or a solid, stable workaround that keeps any site from being terminally broken. I realize OA (v. 2) is still being tweaked and figured out after a pretty big overhaul, but I'm hoping there will be no need to start with a "clean install" if I encounter any errors down the road.

The reason I say "need to do a clean install" is because many people posting here are not knowledgeable enough about Drupal to do full-fledged debugging of a problem. I know it's sort of like "is it plugged in" but honestly, that what happens with a free support forum like this. I just don't have the time to get into nitty-gritty debugging of every Drupal web site. To debug you need to start from a known starting point (a fresh install).

There are lots of ways to handle issues like you describe without needing to wipe out your content and start over. But this isn't the place to have those huge complex support discussions. This is the issue queue for the main OA2 distribution and is for specific reproducible bug reports, patches, etc.

I fully support compatibility with OA2 between release versions (Beta, RCx, Release). But I can only do that for "out-of-the-box" installs. As soon as you start adding additional modules or customizing your site, then I can't promise any sort of compatibility...there are too many variables to deal with.

Try to remember that OA2 is not a simple module. It's a complex distribution of over 180 modules. I am not the maintainer of most of those modules. There is a limit to what I can support here.

In any case, closing this issue as fixed since the Search API issue preventing content from being deleted has been fixed in the latest 2.0 release. For other reproducible issues, please create new issue topics