ProsePoint Express: hosted newspaper website content management software

Error when updating to 0.31

  • strict warning: Non-static method view::load() should not be called statically in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/handlers/views_handler_argument.inc on line 0.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter_node_status::operator_form() should be compatible with views_handler_filter::operator_form(&$form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/modules/node/views_handler_filter_node_status.inc on line 0.
  • strict warning: Non-static method view::load() should not be called statically in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 0.
  • strict warning: Declaration of date_api_filter_handler::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/date/includes/date_api_filter_handler.inc on line 0.
  • strict warning: Non-static method view::load() should not be called statically in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/views.module on line 879.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/plugins/views_plugin_row.inc on line 0.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/plugins/views_plugin_row.inc on line 0.
2 replies [Last post]
xtian
User offline. Last seen 5 years 26 weeks ago. Offline
Joined: 21/08/2009
Posts:

I got the following error during the upgrade process from 0.30 to 0.31:

user warning: Table 'usrdb_xy_prosepoint4.semaphore' doesn't exist query: SELECT expire, value FROM semaphore WHERE name = 'locale_cache_de' in /home/xy/www.xy.com/includes/lock.inc on line 154.

Everything seems to work so far but I am not sure there aren´t any hidden problems.

Thanks for any help
xtian

xtian
User offline. Last seen 5 years 26 weeks ago. Offline
Joined: 21/08/2009
Posts:
No action required?

Just found this: http://drupal.org/node/732024
Maybe this answers the question above.

xtian

beng
User offline. Last seen 4 years 31 weeks ago. Offline
Joined: 27/02/2009
Posts:
Table 'semaphore' doesn't exist query

Hi,

Yes, you are correct (and http://drupal.org/node/732024 describes it well).

If you are also running locale.module on your site (ie. you are using non-english features), then you will get this warning message ...

user warning: Table '...semaphore' doesn't exist query: SELECT expire, value FROM semaphore WHERE name = '...' in .../includes/lock.inc on line 154.

It's safe to ignore this warning this time because the missing table is created immediately during the execution of update.php.

However, if you see this message occurring again after running update.php, please let me know.

Thank you for posting this and for finding the link as well.