drupal.org mkalkbrenner issues
I have a site with 8 sections, resulting in 8 themes. Each section has about 4 or 5 rules for the content to keep the theme correct.
So I would be looking at about 40 rules roughly, maybe a bit less.
Does anyone foresee any problems with this?
This site gets about a million page views a month. Runs on a fairly beefy dedicated server.
When a node is deleted or unpublished, it gets removed from Solr index by the function apachesolr_index_delete_entity_from_index(). However the translated documents in Solr are not being removed.
This is because the Solr query in apachesolr_index_delete_entity_from_index() does not take into account language:$document_id = apachesolr_document_id($entity_id, $entity_type);
$query = "id:"$document_id" OR sm_parent_document_id:"$document_id"";
The solution is very simple, add the original document id to the translated documents, in the field sm_parent_document_id.
I will add a patch for this.
Thank you very much,
When switch from one users node with their theme explicitly set to another users node with their theme set to the detail the theme switches for both an anonymous and registered user.
I have these themekey settings checked as on...
Retain the theme until a new theme is set
Retain the theme until a new theme is set for anonymous users
What am I doing wrong or is this a bug? I see that it has been an issue in the past but there are no posts made for themekey 7.x.
I'm trying to override the admin theme for user/%/edit pages. I first set a themekey rule for that path to use my default theme, but I saw the message that "Seven is the admin theme, which is stronger than themekey rules." So I set admin theme to "default". In themekey rules, everywhere I had referenced "=> Administration theme", I changed it to Seven. Then I added a rule for path_is_admin and also specified Seven. I get an error stating "Theme is not activated." [it would be helpful if the error message gave the theme name.]
When I go to admin pages, I see my default theme, not Seven.
ThemeKey Properties: NOT installed
Cron runs every 30 minutes
Themekey (Cron cleans up page cache) checked
The only enabled theme switching rule : mobile:device = mobile (switch theme to:) FBG
With Caching mode NORMAL enabled:
Mixed. Sometimes site on mobile device displays FBG theme, other times the other blemarine theme.
Similarly: Sometimes site on desktop displays the desired blemarine theme, other times it display FBG that is intended for mobiles
With cache disabled: theme mobile swiching seems ok.
I have been using ThemeKey 7.x-2.5 successfully on my site. I'd like to upgrade to 7.x-3.0-rc2 (required for Browscap integration) but I'm having trouble updating successfully. What are the standard steps / best practices for updating ThemeKey? I do not see 7.x-3.0-rc2 as an option on the Module Update page.
I tried uninstalling 7.x-2.5 using the Drupal Module Uninstall interface (then running Update.php and Cron). This does not remove the ThemeKey options from the Modules list but they no longer seem functional. It also says that ThemeKey is already installed if I try installing again from the Install Module page. Deleting the ThemeKey folder on my server removes the ThemeKey options and I am then able to install ThemeKey again from the Module Install page. If I install 7.x-3.0-rc2 I get Incompatible Version errors on all ThemeKey module options (See attached screenshot for details. The error is: Requires: System (>=7.22) (incompatible with version 7.9).). Installing 7.x-2.5 restores the original functionality and removes the errors.
I have also tried manually updating the ThemeKey folder on my server (replacing it with the 7.x-3.0-rc2 files) but I get the same Incompatible Version error.
We are using Drupal 7.9. Please let me know if you need any additional details or information.
Thanks for your assistance!Recent Files: CommentFileSizeAuthor Screen shot 2014-01-13 at 5.23.08 PM.png192.57 KBladow
I have a question...
I'm currently usiung THEME KEY to identify sections of a site... so depending on the Node Path, it shows different themes to the user.
However, I want to allow a node (say, a contact-us webform) to retain the same theme as the theme from which it was clicked.
So the rule would look like:
drupal:path = "contact-us" ---> CURRENT THEME (and kick out of the rule chain)
How would I accomplish this given that I can ONLY select existing themes or a default theme in the rule, and can't specify it to stay with the current theme if true.
Is there solr 4.6 support version?
This is happening at OG path group/node/#nid/admin/people. Easy fix though. Patch to follow.Recent Files: CommentFileSizeAuthor #3 2161863_og_context_path_fix.patch571 bytesmkalkbrenner #1 2161863-1.patch619 bytessammys
When the user has the ability to choose a theme for their content the "Theme configuration for my content" is collapsed. Can you make it uncollapsed or tell me how to do it?
Role base access to "Let the user select a theme that will be used to display all content she creates."
Can you add a permission that grants / restricts access to "Let the user select a theme that will be used to display all content she creates." I want some, but not all of all my users to have the ability to choose a theme.
After updating to 7.x-1.0-rc2 I see the following error on the status report page:
Apache Solr Multilingual
Could not establish a connection to this solr index. The field bias settings could not be verified.
The "Apache Solr" requirement, however, does not fail. The connection to the solr instance can be established.
Is there a way to configure themekey to match on term list pages, like taxonomy/term/%tid, but NOT on nodes that have that term?
In other words, I have a view that overrides /taxonomy/term/%tid list pages that need a special theme, but when you click on any of the items on that page, I want it to go to a node page that has my default theme. Currently it looks like themekey is matching the node page too if the node is in that taxonomy term. Looking through the issue queue, it appears that many user desire that functionality, but is there a way to disable that feature?
Upon updating the module while it is disabled, a call is done to apachesolr_multiligual_confgen_register_multilingual_variables() which is in the (unincluded) module file.
We get the following error:
PHP Fatal error: Call to undefined function apachesolr_multiligual_confgen_register_multilingual_variables() in modules/contrib/apachesolr_multilingual/apachesolr_multilingual_confgen/apachesolr_multilingual_confgen.install on line 46
Patch atttachedRecent Files: CommentFileSizeAuthor #1 interdiff.txt713 bytesstefan.r #1 apachesolr_multilingual-2147927-installer-1.patch980 bytesstefan.r apachesolr_multilingual-installer.patch1.4 KBstefan.r
Hi, everyone. I am just posting a task for myself to get motivated building up a ThemeKey documentation page. There are many new options and the complexity of this module can be overwhelming -- so, I wanted to help out to make sure people understand how this module works. I only just started this, so, I am cleaning up the existing options contained within the modules themselves. I am still deciding on how to divide it all up. Should we cover Drupal 6? It is a much simpler module but, maybe, it isn't required?
I am posting these into the contributed module section under the documentation section of drupal.org:
Anyway, it is a start...
Upgraded to themekey 3 dev and installed the mobile detect module. Getting these errors after enabling mobile detect:
Notice: Undefined variable: properties in themekey_mobile_detect_themekey_properties() (line 39 of /sites/all/modules/themekey/modules/themekey.mobile_detect.inc).
In log messages - Mobile_Detect() class does not exist
In my status report I get this:
Apache Solr Multilingual - Missing field bias settings of environment ID solr.
This solr index contains new searchable fields. These fields are ignored until you configured and saved the Field biases.
When I click on on the "Field biases" link I get this:
Fatal error: Class 'e' not found in /home/myusername001/mysite001/code/sites/all/modules/apachesolr/apachesolr.module on line 1458
line 1458 is:
$solr = new $class($url);
I'm using the last Apache Solr Search version 7.x-1.6 module.
We need to provide these fields.
I understand that with themekey module activated, users can select theme for their pages from their profile edit page. I thought it would be great if there is a way to make a page that does just that so that there can be more space for the list of themes to grow if we want to. Please kindly guide me on this if it is already something doable. Many thanks for creating this great module.
I've got tons of:
Notice: Undefined index: ss_language in ApacheSolrDocument->__get() (line 305 of Apache_Solr_Document.php)