Drupal 5.x
assessing hosting commpany commentary and enticements ...
The only credible commentary on hosting companies comes from those who can and do provide evidence of their hosted Drupal site, by links included their post, where their drupal.org login identity and drupal.org posting history matches with their linked site and comments. Posts like the recent one for WHB usually appear to be created by shills for the referenced hosting company. As others have noted, shared web hosting business competition has become so intense that there are shills who defame, or at least bad mouth, their competition with hopes they might entice new clients to theirs.
What is apparent from surveying hosting company sites is that most are notorious for incredibly bad service due to a variety of causes. For example, the shared hosting business appears to be a very low margin enterprise, where the primary differentiators are bandwidth and storage promises. Among the big red flags about many hosting companies are their deceptive marketing tactics. There deceptive tactics include bait and switch schemes, a sales pitches that claims a low monthly rate on the surface, which in reality requires yearly pre-payment with a very high cancellation penalty. The world of web hosting bears all the features of a cut throat business environment where the largely anonymous customers come and go with the wind.
Custom image sharpening
Using the imageapi and imagecache 5.x-2.0 it is fairly easy to integrate new image filters.
Firstly, ensure that you have a custom module that you can edit, or create a new one using the two files given below:
================== extra_filters.info ===================
; $Id:
name = Image unsharp mask
description = Misc. custom filters; including unsharp mask, ...
package = Other
version = 0.1===================================================
================== extra_filters.module===================
<?php
/**
* Implementation of hook_imagecache_actions.
*
* @return array
* An array of information on the actions implemented by a module. The array contains a
* sub-array for each action node type, with the machine-readable action name as the key.
* Each sub-array has up to 3 attributes. Possible attributes:
*
* "name": the human-readable name of the action. Required.
* "description": a brief description of the action. Required.
* "file": the name of the include file the action can be found
* in relative to the implementing module's path.
*/
function extra_filters_imagecache_actions() {
$actions = array(
'extra_filters_unsharp_mask' => array(
'name' => 'Unsharp mask',
'description' => 'Unsharp mask using amount, radius and threshold.',
interface translation & locale_source and _target tables
we're trying to translate only the interface of our drupal site to another language (menu's "click here to read more", etc – NOT content).
i started off with the assumption that all string that we stick through a t() function in our templates (we did this in anticipation of this translation effort) would be found as BLOB in the locale_source db table, but that does not seem to be the case.
im basically trying to figure out how we can extract all strings to send to the translators. my idea was dump all BLOB's from the locale_source, send to translators and dump the translated strings in to the locale_target table.
obviously this isnt the best way to go about it?
FieldSet and template views
I am a little bit lost : I am trying to customize a view in drupal 5.7.
I would like my data to be organised in separate fieldsets. To do that, i've used the theme wizard, I have generated the code for the function, something as
function phptemplate_views_view_list_my_view_with_fieldsets($view, $nodes, $type) {
// ...***************************
// ... some code to generate the $items variable
// ... ***************************
$fieldset0 = array(
'#title' => 'Mon title 1',
'#collapsible' => TRUE,
'#collapsed' => FALSE,
'#value' => theme('item_list', $items));
$fieldset1 = array(
'#title' => 'Mon title 2',
'#collapsible' => TRUE,
'#collapsed' => TRUE,
'#value' => theme('item_list', $items));
return theme('fieldset', $fieldset1, $fieldset2);
}
I would like the function to return the multiple fieldset i have generated. What I am missing?
collapsible cck field?
I'm working out a bunch of things.
I am liking the cck table field, but I would like to collapse it. I got the collapsible code module, and that's pretty nice too, but since the table is in its own field, I'm looking into collapsing it. But, a drupally way, not a way that breaks stuff.
Anisa.
watchdog problem
I wonder if anyone can help me out with this? Having upgraded from mySQL 2.3 to 4.0 I now get a page full of errors when I access my Drupal home page.
Here's the first few lines
# warning: mysql_query() [function.mysql-query]: Unable to save result set in /usr/local/home/httpd/vhtdocs/mooli/blogs/includes/database.mysql.inc on line 153.
# user warning: Incorrect information in file: './aggiesurfclub/watchdog.frm' query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE n.nid = 7 in /usr/local/home/httpd/vhtdocs/mooli/blogs/includes/database.mysql.inc on line 172.
# warning: mysql_query() [function.mysql-query]: Unable to save result set in /usr/local/home/httpd/vhtdocs/mooli/blogs/includes/database.mysql.inc on line 153.
There's lots more, but it mostly seems to be a problem with watchdog.frm
Any ideas how I might fix this?
Thanks
Ken
