extend individually-styled channels to include the user profile page and contact page

For the themeing of the View perhaps I could create a new page type and template that printed out my View. Then when the user created this new page it would be themed as he specified because he is the author. The page template itself would then also print the View. As long as I can programatically call the View with the current arguments at that point. Since the View needs the node author name, if the page URL contains the node author name, hopefully I could grab it from there.

Though that makes the installation of numerous themes cumbersome.

To solve this problem I think I can use Viewreference and assign the fieldtype to a node type. Viewreference will also let the admin set a default using PHP code. Thus I could pass the node author's name to the View. Then I could use field_permissions to only allow the Drupal admin to edit this field. Viola, a node themed by the author's preference that displays a View of the author's nodes.

Now I need a solution for the 1) user contact page and 2) the user profile page.

excellent, thanks!

thanks. I hope to test the feature tomorrow.

1. Themekey 7.x-3.x upgraded from 7.x-2.x without error on screen, logs, or php error log. Good.

2. User selected theme evident on their profile and while editing profile. Good.

3. User selected theme evident on their contact form. Good.

4. User selected theme evident on user's blogs and pages and while editing. Good.

5. Tried UNsuccessfully to apply users selected theme to the 'add' page. Instead of staying on the current theme the 'add' page always switched to the default theme. Need help with this.
This is checked ~ Retain the theme until a new theme is set
This is checked ~ Retain the theme until a new theme is set for anonymous users
This is checked ~ Compatibility > Integrate Modules in... Rule Chain > System (Admin theme)
Administration theme set to - 'default theme'

If did notice that there is a new(?) Theme Switching Rule Chain that assigns the wildcard path to the default theme. I don't think I had that rule there before. Did this upgrade automatically add that rule? Why does the rule need to be there? Perhaps that rule makes it so that Themekey always has a theme assignment for every page so that the 'Retain' theme checkbox no longer functions.

6. Wording suggestions...

On page ~ /admin/config/user-interface/themekey/settings/ui
Let the user select a theme that will be used to display all content she creates.
Assign themes from user profile. All content created by a user will be shown to all visitors
using the theme she selected in her profile. This also includes the user's contact
form, profile page, and blog pages.

Let the user select a theme for only her blog pages
Assign themes to personal blogs from user profile. Requires "Let the user select a theme
for her nodes in her user profile" to be activated.

On page ~ /admin/config/user-interface/themekey/settings/compat
This feature seems like it could use more words of explanation. I still don't really understand it.

7. Also, got this error most times after running cron...
Notice: Undefined index: themekey_ui:blog_author_triggers_theme in themekey_cron_clear_page_cache() (line 34 of /home/adminw/public_html/drupal.www.waterpa.com/sites/all/modules/themekey/themekey_cron.inc).

8. Lastly, Got this error when editing an existing page, but deleted the page and started over and didn't see the error again...
===
Notice: Undefined index: article_node_form in drupal_retrieve_form() (line 764 of /home/adminw/public_html/drupal.www.waterpa.com/includes/form.inc).
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'article_node_form' was given in drupal_retrieve_form() (line 799 of /home/adminw/public_html/drupal.www.waterpa.com/includes/form.inc).

hmmm, trying to figure out how to download get the latest commit.

ok - got it.

I copied the three revised files from your git link above and installed.

1. Themekey 7.x-3.x upgrade to 7.x-2.x. Not re-tested, I assume good.
2. User selected theme on their profile and while editing profile. Still good.
3. User selected theme on their contact form. Still good.
4. User selected theme on user's blogs and pages and while editing. Still good.
5. User selected theme on 'add' page. Good
Unchecked ~ Retain the theme until a new theme is set
Unchecked ~ Retain the theme until a new theme is set for anonymous users
Still checked ~ Compatibility > Integrate Modules in... Rule Chain > System (Admin theme)
Administration theme still set to - 'default theme'
Deleted my Theme Switching Rule Chain that assigns the wildcard path to the default theme.
(I may have created that rule and forgot what I did. Rule not needed and deleted).

6. Wording suggestions? I didn't see the changes after updating the three files.

ON PAGE ~ /admin/config/user-interface/themekey/settings/ui

Let the user select a theme that will be used to display all content she creates. Assign (THEME not themes) from user profile. All content created by a user will be shown to all visitors using the theme she selected in her profile. This also includes the user's contact form, PROFILE PAGE, and blog AND OTHER pages. Requires THE PERMISSION "Let the user select a theme for her nodes in her user profile" to be activated.

Let the user select a theme for ONLY her blog pages. Assign (THEME not themes) to personal blogs from user profile. Requires THE PERMISSION "Let the user select a theme for her nodes in her user profile" to be activated.

ON PAGE ~ /admin/config/user-interface/themekey/settings/compat
This feature seems like it could use more words of explanation. I still don't really understand it.

ON PAGE ~ /admin/people/permissions
Assign theme to own content. Let the user select a theme that will be used to display all content she creates.

You may want to delete that last sentence and let that one permission clearly apply to both the blog only AND the all content user theme selection options.

7. Got an error after running cron. Super, error is gone.
8. Lastly, got another error... Agreed, unrelated.

QUESTIONS
1. What additional testing ideas do you have? Hopefully you are testing as well.
2. Hoping to move this release out of alpha before I use in production. What is the time frame for that and what other 'alpha' changes are in 3.x?

super. I'll install alpha 2 as soon as I see it.

I just installed 3.x-alpha2. It works great, thanks. The user's selected theme was displayed to them and other users when viewing blog pages, other pages, their profile, their contact form, and also while they edited their pages or added pages. I also saw your fixes to the wording. I also changed the user's theme selection and the theme changed immediately for them and other users on all pages. Cron also runs successfully. No errors observed in the Drupal logs or PHP error log. Looks good.

You say above in #7

If you want to switch the user/#uid/edit form as well, you have to disable core's administration theme feature completely. Or use ThemeKey Compatibility to integrate the System module with ThemeKey and let themekey_ui:author_triggers_theme take precedence over themekey_compat:module_system_triggers_theme.
(I recommend the second approach)

All the above tests worked fine for me without even enabling 'Themekey Compatibility'. However, maybe that is because at '/admin/appearance' I have 'Use the administration theme when editing or creating content' unchecked. Is that what you mean by 'disabling core's administration theme feature completely'? Also why is one method preferred over the other?

Also note on this last round of tests I fully uninstalled Themekey and re-installed fresh.

If I understand properly you may want to make these changes...

@ /admin/modules
Change this...
"Integration of different theme switching modules into ThemeKey and its theme switching rule chain."
To this...
"Integration of additional modules to allow ThemeKey to retain control in the theme switching rule chain when Administrative, Views, and other theme selection options are also used."

@/admin/config/user-interface/themekey/settings/compat
Expand this...
"Integrate Modules in Theme Switching Rule Chain"
To this...
"Integrate Modules in Theme Switching Rule Chain. These modules allow ThemeKey to retain control in the theme switching rule chain when Administrative, Views, or other theme selection options are also used."

@/admin/config/user-interface/themekey/settings/ui
Expand this....
"Assign themes from user profile. All content created by a user will be shown to all visitors using the theme she selected in her profile. This also includes the user's contact form, profile page, and blog pages."
To this....
"Assign themes from user profile. All content created by a user will be shown to all visitors using the theme she selected in her profile. This also includes the user's contact form, profile page, and blog pages. If Administrative theme selection options are used ThemeKey Compatibility must be enabled and configured to allow ThemeKey to retain control in the theme switching rule chain for 'edit' and 'add' pages."

* minor grammatical note. It is curious that in English there is no gender neutral personal pronoun. So unfortunately it forces one to choose between 'he' or 'she'. The common solution is to go plural. So this "she selected in her profile" would be this "they selected in their profile".

what work remains to call this feature closed (fixed)?