Garrett:
Here is a 6 minute video of my creating a
40-character subtheme and the deadly errors it produces;
and my recovering from that error
and then creating a 39-character error free subtheme--
just so you can see what I did.
http://www.great-grandma.com/zen-issues/zenophile-7-1/zenophile_7_1-40_a...
Is it BlueHost.com?
I don't know.
===
ERRORS....
Additional uncaught exception thrown while handling exception.
Original
PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'event' at row 1: INSERT INTO {flood} (event, identifier, timestamp, expiration) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3); Array ( [:db_insert_placeholder_0] => a23456789x123456789t123456789r123456789f_rebuild_registry_warning [:db_insert_placeholder_1] => 71.8.198.198 [:db_insert_placeholder_2] => 1305435788 [:db_insert_placeholder_3] => 1305439388 ) in flood_register_event() (line 1149 of /home1/greatgr2/public_html/d7014/includes/common.inc).
Additional
PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'event' at row 1: INSERT INTO {flood} (event, identifier, timestamp, expiration) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3); Array ( [:db_insert_placeholder_0] => a23456789x123456789t123456789r123456789f_rebuild_registry_warning [:db_insert_placeholder_1] => 71.8.198.198 [:db_insert_placeholder_2] => 1305435788 [:db_insert_placeholder_3] => 1305439388 ) in flood_register_event() (line 1149 of /home1/greatgr2/public_html/d7014/includes/common.inc).
Comments
Comment #1
christopher james francis rodgers commentedComment #2
Garrett Albright commentedYour link seems to be 404ing, which is kind of a bummer because I'm kind of flattered you're going through all this trouble.
Comment #3
christopher james francis rodgers commentedGarrett:
My apologies: My error: Re-uploaded: Same link:
http://www.great-grandma.com/zen-issues/zenophile-7-1/zenophile_7_1-40_a...
-Chris
Comment #4
Garrett Albright commentedOkay, well, that clears up your process a bit, but I still don't know what exactly is happening or why, nor can I replicate it. Nothing about creating or switching themes should be touching the flood table at all, nor should things be colossally failing if a field value is too long like that.
So I guess the only thing I can suggest is to just use a shorter theme system name and move on. Sorry.
Comment #5
christopher james francis rodgers commentedGarrett:
Thanks for your time.
Your comments about "flood table" are beyond me
and my no-php-knowledge. I simply made the video so
there would be no questions in your mind about
what I did to produce the errors.
Believe me: I will not be using 40-character "System name"s
although I did like your idea of restricting the input in that field-box
to 39 characters or less for other new-users; although I have no idea
how you do that.
The simplest solution I can think of would be to change the text...
"The machine-compatible name of the new theme. This name may
only consist of lowercase letters plus the underscore character."
...to include a warning.
Additionally, I am hoping that you consider changing that text
to more accurately reflect the true limitations of the "System name";
for example to, ...
"The machine-compatible name of the new theme. This name may
only consist of lowercase letters (a-z), numerals (0-9),
and the underscore character. It must begin with a letter and should not exceed
39 characters in length. This will be the name of the directory (folder) containing
your Zen sub-theme, and will be created at
[your-drupal-7-root]/sites/all/themes/[machine_name_folder]."
Thanks again for the time and aggravation saving dream that Zenophile is
for side-bar placement and width specifications.
All the very best to you.
-chris
###
Comment #6
Garrett Albright commentedLike I said, though, I can never replicate this, and wherever the problem is, I'm 95% sure it does not lie with Zenophile. Therefore, I will not be changing anything about Zenophile.
Comment #7
christopher james francis rodgers commentedGarrett:
I just tested Zeno71 with D7.2 and zen731 manual install at BlueHost
(SimpleScripts is still at D7.0); and the problem persists.
My only concern with this issue is that you could easily forewarn new users
in your machine name description about the possible problems of using
40 (or more) characters in the system name;
or that you program the restriction to return an error/ warning message
just as what happens when the user tries to, for example,
use upper-case letters/ dashes/ spaces...
I am aware that it might be only a rare occurrence
but as you have seen, it can happen.
Wishing you the best
-c
Comment #8
christopher james francis rodgers commentedGarrett:
I installed Drupal 7.7 locally on my computer
for the very first time last week using Damp
on Windows XP and was surprised to find that my
D7 installation crashed when I
- used a 40-character system-name
when I created a Zenophile sub-theme
- and set that theme as the administrative theme.
I had previously been guessing that your inability to replicate this problem
was probably due to your running D7 locally.
I also replicated the Crash on-line at a BlueHost.com
test site again yesterday using D7.7.
I installed it in a site sub-folder that I named using 40-characters.
As a result, the Zenophile "Create Zen sub-theme" "system name * fieldbox,
displayed a default "system name" name was indeed in excess of 39-characters,
and the sub-theme I created did Crash the site when I set that theme
as the "admin theme".
==============
Notes unrelated to this issue...
By the way, Zen 7.x-5.x-DEV from a day ago or so
seems to be okay with Zeno 7.1.
-------------------
I was surprised to find last week when using Zeno 7.1
that the order of CSS in "View source" on my web page
was not as I had remembered it had been when
I first started using Zenophile.
As I remember it from a couple of months ago
I thought it used to end with
...
zen_midnight.css
fresh.css
print.css
.
But I see that it now ends with
...
print.css
zen_midnight.css
fresh.css
sidebars.css
.
I am wondering if you are aware of this change
since I had always thought it brilliant of you to have
fresh.css last (...not counting print.css).
---------------
I have given up on any hope of using zen_midbight
as an administrative theme because of contrib modules
CSS habit of specifying either only 'color' or 'background-color'
for their configuration pages based on the assumption that
admins were using white background; thus rendering test illegible
when I had Midnight as Admin theme.
("Views" I think it was that I first found to be a problem)
-------------
In addition to my collection of some weeks ago, on a difference Issue page:
I have found one or two additional instances where Midnight
renders text illegibly when it is being used only as
site 'default' theme...
... or was it that I was also using Midnight to "edit / create Content"....
... I forget at the moment, as my collection of *.css files I need to go through
exceeds ten....
In any case, it is my intent to compile that collection
and present it to you in the near future
in as succinct a form as possible,
although not likely in some standard Drupal revision style
since that learning curve seems to me would take me
months to learn... unless you can steer me to a quicker path
to your preferred style of presentation by me to you
on my findings.
----
All the best
-chris
PS: I added a Child Page to your Zenophile handbook page
outlining all of the details I felt relevant
to your options available when creating a zen sub-theme.
The entire Drupal community would benefit, I think,
from your reviewing (and Please, Editing: if necessary < Likely .. lol)
that page of mine.
Thanks. I do love not having to edit CSS
to adjust sidebars placement and widths
thanks to you. You 'da man.