Edit node content using the H5P module in Open Atrium, content not saved

Did you make any other changes appart from installing the H5P module in your OA installation?

Well, nobody ever said Atrium was fully compatible with every other Drupal module. It's up to that module author to make their module more compatible. Atrium uses modules such as Panels and Organic Groups that can change behavior and the H5P module needs to account for that.

But since Atrium doesn't "own" these modules (like Panels, OG, etc), it's not something we can fix here in this issue queue. This really should be posted to the H5P issue queue.

Hi, JohanFeuillet, you should be able to save it. I tested it before. Are you sure it is not "showed" instead of not saved? Check my post before: https://www.drupal.org/node/2682889. Hope this help.

Hi JohanFeuillet,

In my installation, h5p content can be saved and modified (in three different test installations). Ddi you try to check your log message?

hosais

Hi Mike,

Let me start by saying OA 2.6 is a huge step forward from 2.54 ... I am getting the same problem here I can't save or edit new contents.. I think it has something to do with the panels everywhere module I read that somewhere... the hierarchical select module isn't working either I feel it is for the same reason, as everything was working great until 2.54... This happened after the update to 2.60. OA is awesome and we love it.

Best Regards,
F

Hi everyone,
The following patch for panels everywhere works, I tested it..
https://www.drupal.org/node/1139918

diff --git a/plugins/tasks/site_template.inc b/plugins/tasks/site_template.inc
index 939d421..5d7feb9 100644
--- a/plugins/tasks/site_template.inc
+++ b/plugins/tasks/site_template.inc
@@ -82,6 +82,13 @@ function panels_everywhere_site_template_get_base_contexts($task, $subtask, $pla
// this.
if ($page) {
$node = _panels_everywhere_find_context($page['contexts'], 'node');
+ // If the node object is a node form then blank out the context and
+ // replace it with a generic object. This is to work around a limitation
+ // in Panels and may introduce regressions.
+ if ($form_context = ctools_context_get_form(array($node))) {
+ $node = ctools_context_create_empty('node');
+ }
+
$account = _panels_everywhere_find_context($page['contexts'], 'user');

// We're already including the logged in user. We don't want that to
@@ -94,6 +101,12 @@ function panels_everywhere_site_template_get_base_contexts($task, $subtask, $pla
// This context will only be loaded if the Taxonomy module is loaded.
if ($load_taxonomy) {
$term = _panels_everywhere_find_context($page['contexts'], 'entity:taxonomy_term');
+ // If the term object is a term form then blank out the context and
+ // replace it with a generic object. This is to work around a limitation
+ // in Panels and may introduce regressions.
+ if ($form_context = ctools_context_get_form(array($term))) {
+ $term = ctools_context_create_empty('entity:taxonomy_term');
+ }
}
}
else {

Added this patch to panels_everywhere in Open Atrium. Committed to 6a176c3 in oa_site_layouts