Alexisyes

Drush make files online generator

Alex — Tue, 13 Mar 2012 19:47:52 +0000

Tags

drush

Aegir tasks are not running

Alex — Mon, 12 Mar 2012 19:41:17 +0000

Whenever this happens, login to your aegir server, change directory to hostmaster installation and try to run:
drush @hostmaster hosting-dispatch --debug
If this command will return you any errors - first you need to fix them. After that, you'll be fine.

Tags

aegir

Update to Drupal 7

Alex — Mon, 14 Feb 2011 15:21:19 +0000

Finally i updated my blog to Drupal 7 from Drupal 6.20. Wasn't hard at all, but still requires some skills and understanding of Drupal internals. Also site theme is now changed to Sky which is a nice CSS3 + HTML 5 powered theme implementing 960gs framework.

Drush doesn't respect ssh-options in some commands

Alex — Tue, 17 Aug 2010 08:32:06 +0000

If your servers using non-standart SSH port, then Drush can fail using aliases for some commands (in my case it was sql-sync). The fix is already committed to HEAD, but until then you can apply patch from here
http://drupal.org/node/820514

CSS Aggregation fails in Drupal 6.19

Alex — Mon, 16 Aug 2010 08:09:32 +0000

And the fix is - convert all your CSS files into UTF-8 encoding.
From here: http://drupal.org/node/881132

Tags

fix

Problem with Eclipse PHP project

Alex — Tue, 29 Jun 2010 15:37:30 +0000

Symptoms:
1. XDebug is not working
2. Code completion is not working
3. "Go-to definition" is not working (CTRL+Click on function name)
4. Eclipse do not see your PHP errors

Usually this means that Eclipse do not know that your project is PHP type, sometimes it happens when you create a project via checkout from SVN. So, what to do:
1. Create new PHP project and save it. Check if everything working with the new project.
2. Check .project file in the root of the new project directory you just created. You should see something like this:

New PHP Project

org.eclipse.wst.validation.validationbuilder

org.eclipse.dltk.core.scriptbuilder

org.eclipse.php.core.PHPNature

3. Open .project file from your old non-working project. See the difference? There are no validators definitions and nature of project is unknown
4. Copy contents from new .project file to old one. Make necessary modifications (like proper project name). Save.
5. Restart Eclipse.

HTTP error 0 in apachesolr_autocomplete

Alex — Mon, 21 Jun 2010 11:04:11 +0000

If you didn't know it before - there is a nice module which will provide autocomplete functionality to all of the search forms on your Drupal site. Recently i have installed this module on our development box and everything was pretty fine. Today i pushed a new version of the site to the preproduction box and autocomplete stops working with errors:
PHP Fatal error: Uncaught exception 'Exception' with message '"0" Status: Request failed' in /sites/all/modules/apachesolr/Drupal_Apache_Solr_Service.php:272 Stack trace: #0 /sites/all/modules/apachesolr/SolrPhpClient/Apache/Solr/Service.php(964): Drupal_Apache_Solr_Service->_sendRawGet('http://192.168....') #1 /sites/all/modules/apachesolr/apachesolr_search.module(246): Apache_Solr_Service->search('finance', 0, '20', Array) #2 /sites/all/modules/apachesolr/drush/apachesolr.drush.inc(145): apachesolr_search_execute('finance') #3 [internal function]: apachesolr_drush_solr_search('finance') #4 /usr/share/drush/includes/drush.inc(51): call_user_func_array('apachesolr_drus...', Array) #5 /usr/share/drush/drush.php(90): drush_dispatch(Array) #6 /usr/share/drush/drush.php(40): drush_main() #7 {main} thrown in /sites/all/modules/apachesolr/Drupal_Apache_Solr_Service.php on line 272 Drush command could not be completed.

I did some investigation and the problem was in the size of headers which were getting passed to solr. Fix in server.xml:

Change:
connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8"/>
To:
connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8" maxHttpHeaderSize="8192"/>
And restart Tomcat.

Related issues on Drupal.org:
"0" Status: Request failed

Helpful handbook page:
Troubleshooting

search_index table is too big while using Apache SOLR?

Alex — Mon, 21 Jun 2010 08:55:19 +0000

The reason - core search module is still indexing content. The solution - go to admin/settings/search and set "Number of items to index per cron run" to 0. This will prevent core search module to work. And to clear the tables you can press "Re-index site" button.

Tags

drupal, solr, search

Function path_to_theme() can catch you

Alex — Tue, 30 Mar 2010 14:53:02 +0000

Return the path to the current themed element.
The main thing is that if you will call it from the module preprocess hook - it will return the
path to the module.

So if you want to keep your logic in code and still be able to help your designer/js-coder (who doesn't know for sure where is the custom module files, but know the theming a bit):

drupal_add_js(drupal_get_path('theme', variable_get('theme_default', 'garland')) ."/js/cooljavacriptfilehere.js");

From api.drupal.org:
It can point to the active theme or the module handling a themed implementation. For example, when invoked within the scope of a theming call it will depend on where the theming function is handled. If implemented from a module, it will point to the module. If implemented from the active theme, it will point to the active theme. When called outside the scope of a theming call, it will always point to the active theme.

Managing comments access on the fly

Alex — Tue, 23 Mar 2010 10:54:59 +0000

As you may already know, you can control the comments module behavior with user permissions and with per node-type settings. But what if you want to change the node comments access on the fly?

The problem:
On some nodes i want to disable the comment form for current user, but show him the comments. It is possible with the default comment settings of this node type or with access permissions. But what if the permissions are configured for full read-write access for the current type of node and current user have permission to post comments?

Solution:
No normal solution for the moment. The blocker is comment_render() function which is not granular enough for checking for changed permissions on the fly. There are temporary solutions with templating system which requiring overriding default box.tpl.php and checking for the access in this template (it is very ugly, because the point of templates is to separate site logic from display) and overriding default comment callbacks in comment/reply/%nid menu item with hook_menu_alter().

The point of this post? There are a lot of small common things which are very hard to implement using current state of some core modules. Hope that Drupal 7 will fix that.

Tags

drupal, comments, access