By mercyme on

Hello all! Thanks in advance for your help with this question :-)

We've been seeing a strange error quite a bit lately when we run update.php, and I'm just wondering if it has any special meaning (since the error itself isn't particularly informative).

The error we're seeing is:

: in (line of ).

I'm guessing this is a template used to generate error output that simply isn't being populated. My question is: why? Are there known situations where this specific message would be displayed? Or maybe, are there any general situations - database connectivity failure, file parsing failure, etc. - that would cause this specific message?

Thanks again for your help, over all we're really enjoying Drupal so far!

⋅ Categories: Drupal 6.x

Comments

ratioswitch’s picture

ratioswitch commented

I'm also seeing the same error when running update.php.
: in (line of ). =>
In fact, I see 48 lines of this same error when viewing http://mysite.com/update.php?op=info

After clicking "Continue" on the Drupal database update page and "Next" on the listing of module versions I again see a the same error output but this time with 192 lines of:
: in (line of ). =>

...followed by these 3 errors:

Notice: Undefined variable: view in views_import_views_default_views() (line 15 of /mnt/www/html/username/docroot/sites/all/modules/views_import/views_import.views_default.inc). 

Notice: Undefined property: stdClass::$old_type in modalframe_cck_editor_node_type() (line 123 of /mnt/www/html/username/docroot/sites/all/modules/modalframe_cck_editor/modalframe_cck_editor.module). 

Notice: Undefined property: stdClass::$old_type in modalframe_cck_editor_node_type() (line 125 of 
/mnt/www/html/username/docroot/sites/all/modules/modalframe_cck_editor/modalframe_cck_editor.module).

...followed by another 49 lines of:

: in (line of ). =>

I'm not sure what $old_type means however, the good news is that my Drupal DB updates without any other apparent issues. Strange is an understatement.

@mercyme, any updates on this issue for you?

Thanks,
_rs

dman’s picture

dman commented

Due to the utter weirdness of this error, my case is *probably* not the same as anyone elses, but I managed to trigger this.

I somehow unpacked a theme directly into my themes directory (a bad copy) without it getting into a named subfolder.
On top of that, I had a subtheme that depended on that theme - which did land in the themes folder in a subfolder.
Not sure how badly that confused the system, but after enabling the subtheme (which was allowed, as the supertheme was nearby) actually *using* the theme threw some illegalities as the supertheme wasn't really registered right.

Like I say - maybe not related, BUT I did get the error : in (line of ). until I saw what my problem was.

My f***ed up install

sites/all/themes/
sites/all/themes/mastertheme.info (mastertheme)
sites/all/themes/template.php (mastertheme)
sites/all/themes/page.tpl.php (mastertheme)
sites/all/themes/{etc} (mastertheme)
sites/all/themes/subtheme/subtheme.info
sites/all/themes/subtheme/template.php
sites/all/themes/subtheme/page.tpl.php
sites/all/themes/subtheme/{etc}

Then I enabled subtheme. :-/

.dan. is the New Zealand Drupal Developer working on Government Web Standards

ratioswitch’s picture

ratioswitch commented

Just a quick update here, so no epiphany (or solution) yet. At least not exactly an ideal solution.

I was able to clear up the output of : in (line of ). => when I run update.php by disabling the Translation Management (TM) module. I installed my D6 site in English and added Spanish during the installation process. While the TM module was not included in my base install of D6, some basic translation modules (core) were enabled. I believe this included the Locale and Content Translation modules?

FYI, TM was posted by iCanLocalize and maintained by brucepearson and jozik.

I installed Translation Overview (TO) and TM in the beginning phases of site development (as well as Language Switcher Dropdown, CCK translation, Block translation, Translation Table, Transliteration and a few other multi-lingual helper modules) however, only TM seemed to change the error output when disabled.

Once I figured this out, I could toggle to error output:

  • Enable TM, run update.php and the : in (line of ). =>-error would appear.
  • Disable TM, run update.php again and no more error.
  • Re-enable TM, run update.php yet again and the : in (line of ). =>-error would re-appear.

I have no idea how one would reverse-engineer the Translation Management module to track down why this is occurring or what module setting or custom configuration within my particular site could possibly be the culprit in generating this strange error.

Perhaps some of the above could help shed some light on the topic?

Cheers!