According to the theme admin page, the OpenChurch theme requires both Fusion core and Skinr, but the Skinr module is not being installed by drush make using the OpenChurch profile. I think the following changes should be made to add and enable Skinr:
In openchurch.make add

    projects[skinr][subdir] = contrib

and in openchurch.info add

    dependencies[] = skinr
    dependencies[] = skinr_ui
    dependencies[] = skinr_panels
CommentFileSizeAuthor
#18 openchurch_defaults.strongarm.inc_.zip1.93 KBCode Monkey

Comments

Code Monkey’s picture

Code Monkey commented

I believe Fusion Accelerator is being used instead for the 7.x branch.

drupalninja99’s picture

drupalninja99 commented
Status: Active » Closed (won't fix)

Correct we are using fusion accelerator in D7.

dude4linux’s picture

dude4linux commented

In that case, references to Skinr should be removed from openchurch_theme.info, block.tpl.php, and panels-pane.tpl.php. Just a suggestion to reduce confusion.

drupalninja99’s picture

drupalninja99 commented
Status: Closed (won't fix) » Fixed

Good catch! I have removed those references in head.

dude4linux’s picture

dude4linux commented

@drupalninja99
How can I access HEAD using git? I'm trying to install using drush make and drush site-install with a site stub file like this:

api = 2.x
core = 7.x
projects[] = drupal

projects[openchurch][download][type] = git
projects[openchurch][download][profile] = contributions/profiles/openchurch
projects[openchurch][download][revision] = 7.x-1.x

changing the revision to HEAD or 7.x-1.x-dev results in downloading the 6.x version of the profile and modules.

drupalninja99’s picture

drupalninja99 commented

I think what you put is right.

drupalninja99’s picture

drupalninja99 commented
Version: 7.x-1.x-dev » 7.x-1.7-alpha1

This is fixed in 1.7-alpha1 - now downloadable from the project page!

ajsloan’s picture

ajsloan commented
Title: OpenChurch Theme requires Skinr module » OpenChurch Installation Issues and Error Messages
Version: 7.x-1.7-alpha1 » 7.x-1.x-dev

I'm receiving the following errors after installing open church. I know I can turn off error messages but I'm wondering why so many errors. I've been trying to do a successful install of Open Church for 2 days. Anyone else having installtion issues.

Notice: Undefined property: stdClass::$did in panels_fusion_apply_preprocess_index_handler() (line 65 of /home1/austinsl/public_html/homelessadvocacyministry/profiles/openchurch/modules/contrib/fusion_accelerator/fusion_apply/modules/panels.fusion.inc).
Notice: Undefined property: stdClass::$did in panels_fusion_apply_preprocess_index_handler() (line 65 of /home1/austinsl/public_html/homelessadvocacyministry/profiles/openchurch/modules/contrib/fusion_accelerator/fusion_apply/modules/panels.fusion.inc).
Notice: Undefined property: stdClass::$did in panels_fusion_apply_preprocess_index_handler() (line 65 of /home1/austinsl/public_html/homelessadvocacyministry/profiles/openchurch/modules/contrib/fusion_accelerator/fusion_apply/modules/panels.fusion.inc).
Notice: Undefined property: stdClass::$views_php_3 in views_php_handler_field->render() (line 223 of /home1/austinsl/public_html/homelessadvocacyministry/profiles/openchurch/modules/contrib/views_php/plugins/views/views_php_handler_field.inc).
Notice: Undefined property: stdClass::$views_php_3 in views_php_handler_field->render() (line 223 of /home1/austinsl/public_html/homelessadvocacyministry/profiles/openchurch/modules/contrib/views_php/plugins/views/views_php_handler_field.inc).
Notice: Undefined property: stdClass::$did in panels_fusion_apply_preprocess_index_handler() (line 65 of /home1/austinsl/public_html/homelessadvocacyministry/profiles/openchurch/modules/contrib/fusion_accelerator/fusion_apply/modules/panels.fusion.inc).
Notice: Undefined offset: 1 in superfish_contents() (line 484 of /home1/austinsl/public_html/homelessadvocacyministry/profiles/openchurch/modules/contrib/superfish/superfish.module).

drupalninja99’s picture

drupalninja99 commented

You will want to turn off your notices in php.ini or in settings.php. This is the line you would add to settings.php:

error_reporting(E_ALL & ~E_NOTICE & ~E_STRICT);

I used to add this myself when I was doing the packaging but now that Drupal is doing it, people will have to add it manually.

Code Monkey’s picture

Code Monkey commented

The "Notice: Undefined property: stdClass::$did" errors are caused by the panel not residing in the database. Per merlinofchaos, the did is a database identifier. Once the page / panel is saved into the database, this specific error is not shown.

The next thing is replacing the views_php dependencies and we will be left with the superfish_contents warning.

Code Monkey’s picture

Code Monkey commented
Status: Fixed » Needs work
drupalninja99’s picture

drupalninja99 commented

re: "Notice: Undefined property: stdClass::$did" - that's kind of an annoying feature, it seems like he would be able to handle the 'feature-ized' version of the panel. I am not sure the best way to handle that just yet, bc the point of exporting a panel to a feature is that it doesn't reside in the database initially unless it's customized.

drupalninja99’s picture

drupalninja99 commented

Added issue for fusion accelerator:
http://drupal.org/node/1493610#comment-5778204

Looks like superfish also has an issue.

drupalninja99’s picture

drupalninja99 commented

Added superfish issue: http://drupal.org/node/1498728

The views php thing will be fixed in the views_php ticket.

Code Monkey’s picture

Code Monkey commented

I found a way to remove the warning regarding the superfish issue. I went to Structure > Blocks > Superfish 1 (Superfish) > Configure. Without making any changes to this block, I just clicked Save Block.

Prior to this, I noticed the variable table included only five variables regarding superfish. These are the same variables listed in the /profiles/openchurch/modules/features/openchurch_defaults/openchurch_defaults.strongarm.inc file. However, once I saved the block, the number of variables in the variable table regarding superfish jumped to 43.

I then looked at recreating the Feature for the Openchurch Defaults feature to include the additional superfish* variables. Once I updated the openchurch_defaults.strongarm.inc file to include these additional variables, the warning disappeared on a fresh install.

drupalninja99’s picture

drupalninja99 commented

Can you attach that defaults file to this ticket? That would save me some time. Good work code monkey!

Code Monkey’s picture

Code Monkey commented

I can but it will be later tonight. I am away from my test machine until then.

Code Monkey’s picture

Code Monkey commented
StatusFileSize
new openchurch_defaults.strongarm.inc_.zip1.93 KB

Here is the updated file you requested.

drupalninja99’s picture

drupalninja99 commented

ok I fixed this in dev by changing superfish_menu value to be main-menu:0 instead of main-menu.

Still haven't fixed the panels notices yet, they directed me to this issue: http://drupal.org/node/1373296

This hasn't gotten resolved yet.

drupalninja99’s picture

drupalninja99 commented

Need to see how many of these notices we're still getting.

drupalninja99’s picture

drupalninja99 commented
Status: Needs work » Needs review

ok I believe these homepage noticed are fixed in dev

drupalninja99’s picture

drupalninja99 commented

I rolled in a patch I uploaded here: http://drupal.org/node/1373296. I thought I was uploading it to this ticket, but ended up submitted it to the actual fusion apply ticket.

drupalninja99’s picture

drupalninja99 commented
Status: Needs review » Fixed

These have been fixed for a while

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.