Adding an index on the source column of the locales_source table seem
to increase performance.
See here http://drupal.org/node/48563
I think this is worth considering for 4.7.
This issue stems from Killes' comment [
http://drupal.org/node/46306#comment-71971 ]. Should form field
maxlengths be consistent with corresponding database field sizes or
should unicode encoding be accounted for?
This is especially in light of the fact that 4.7 now converts all
existing databases to UTF-8, but also retains support for (MySQL)
3.23.58.
Or should we just not use maxlengths at all?
Thanks
-K
P.S Please reply on the issue page: http://drupal.org/node/48510
Hi,
I'm using the 4.7 beta4 and the latest flexinode HEAD. When I try to
apply the filters on the fields with this method
$node->flexinode_97=check_markup($node->flexinode_97,$node->flexinode_97_format,FALSE);
the filters aren't applied .
In the body and teaser, everything is OK. What am I do wrong?
--
Aries
Dear all,
When i created a container for Forum,I don't need to become link name of
container itself.Unfortunetly name of container is become a link.
Please guide me.....
Dear all,When i wanna import a PO file,I recv following error:
*Fatal error*: mime_magic could not be initialized, magic file
/usr/share/file/magic.mime is not available in
*/var/www/iossd/includes/file.inc* on line *14
Please help me,,,
*
Hi, I am using Siege to load test the file caching patch. Siege
supports posts, http://www.joedog.org/siege/misc/FAQ.php#9.
Here is what I have come up with discussing this in #drupal
http://localhost/~kieran/drupal/?q =node/add/page POST edit%5Btitle%
5D=title&edit%5Bbod y%5D=body&edit%Bform_id%5D=page_no de_form&op=Submit
But it doesn't submit. If anyone could successfully submit any
content to head using a HTTP post I would appreciate it if you could
pass it along.
Thanks,
Kieran
Hi, this is my first post to this list, please let me know if I am I out of
line in any way.
This may be a bigger issue than just the event.module
If the suggested fix for event.module works, then logically, the same sort
of fix will need to be made to image.module and forum.module and probably
some other modules.
I think killes is correct with his statement of
"The rewriting of the query fails as it isn't in the form the regexp
expects"
The regexp in question is in the db_rewrite_sql function.
This function and its associated hook IMHO provide one of the greatest
capabilities to this CMS helping to set Drupal high above the rest. And I
am so excited to see that it has been expanded to include vocabularies and
terms in version 4.7 (thank you! drupal developers).
Here are some thoughts on the issue, it is a little mind-numbing I know and
I am sorry.
Can someone let me know if I am being clear and also let me know if I am
just way off base.
I think that the db_rewrite_sql function needs to be more explicit in terms
of what sort of SQL statements it accepts for the $query value. I also
think that it needs to be very specific in terms of what values are allowed
for the $primary_table and $primary_field values.
For example, with node list queries, I think the $primary_table must be
'n', the $primary_field must be 'nid' and the $query value must be in the
format SELECT X...X FROM {node} n X...X or there are potential problems.
Looking at the example code posted in drupaldocs for hook_db_rewrite_sql()
at http://drupaldocs.org/api/head/function/hook_db_rewrite_sql. The sample
asks if table 'n' is the $primary_table and if not adds it to the join
clause. If two modules implemented the hook following that example,
checking for the existence of table 'n' and both were enabled on the same
site and the $primary_table was 'f' (or 'forum', or 'node' etc. as outlined
as acceptable values for db_rewrite_query) the resulting query would be
SELECT X...X FROM {forum} f INNER JOIN {node} n ON f.nid=n.nid INNER JOIN
{node} n ON f.nid=n.nid X...X which results in ERROR #1066 - Not unique
table/alias: 'n' So, therefore, I also think that any module implementing
the hook needs to be aware of potential alias conflicts and should make
sure to alias tables with a name that won't conflict with someone elseâs
module.
If interested in more information and more thoughts, please see these three
posts...
Bad interaction with MySQL 5 & Image & Event modules
http://drupal.org/node/40623
SQL error when anonymous: Unknown column 'n.nid'
http://drupal.org/node/46864
Error with node access modules and mysql 5
http://drupal.org/node/43735
Thank you, I hope I haven't wasted anyoneâs time.
Randall
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
Hello,
for your information, I asked Gerhard (killes) to take over the
administration of CVS accounts. This involves approving CVS
accounts, fixing CVS passwords, etc. If it is too much work for
Gerhard, he'll involve more people. Gerhard has been helping out
with this for many weeks, and we've been working together on
improving the CVS integration scripts we use on drupal.org.
--
Dries Buytaert :: http://www.buytaert.net/