error?

8 replies [Last post]
akhter
User offline. Last seen 6 days 22 hours ago. Offline
Joined: 20/02/2010
Posts:

i am getting this error when i an in content type area, my pp version is 0.31

i dont know about it,

 

  • warning: Illegal offset type in isset or empty in /home/etalaatc/public_html/includes/common.inc on line 912.
  • warning: preg_match() expects parameter 2 to be string, array given in /home/etalaatc/public_html/includes/bootstrap.inc on line 777.
beng
User offline. Last seen 1 hour 50 min ago. Offline
Joined: 27/02/2009
Posts:
...

Hi,

Did you do anything recently which may have triggered this error?

Did you just attempt an upgrade to 0.31? If so, did you run .../update.php? If not, please visit .../update.php on your site. You must run update.php during the upgrade to 0.31.

Can you tell me which url on your site gives this error?

akhter
User offline. Last seen 6 days 22 hours ago. Offline
Joined: 20/02/2010
Posts:
pp 0.31

i am etting error when i visit mange field page

http://dailyetalaat.com/admin/content/node-type/story/fields

in admin section

my pp is 0.31 not updated

 

  • warning: Illegal offset type in isset or empty in /home/etalaatc/public_html/includes/common.inc on line 912.
  • warning: preg_match() expects parameter 2 to be string, array given in /home/etalaatc/public_html/includes/bootstrap.inc on line 777.
please help
beng
User offline. Last seen 1 hour 50 min ago. Offline
Joined: 27/02/2009
Posts:
Well, can you please run

Well, can you please run update.php on your site?

Visit http://dailyetalaat.com/update.php and follow the instructions there.

akhter
User offline. Last seen 6 days 22 hours ago. Offline
Joined: 20/02/2010
Posts:
already done
i already done but i am not able to update any thing it says 0 update
beng
User offline. Last seen 1 hour 50 min ago. Offline
Joined: 27/02/2009
Posts:
...

> i already done but i am not able to update any thing it says 0 update

That's good. It means your database schema is up to date so we can rule that out as a cause.

I suspect your two error messages are caused by custom code indirectly calling the t() function (to do a translation) incorrectly (and supplying a non-string parameter when a string parameter is required). Can you check in your theme and any other custom code of yours to see if there is anything suspicious?

Other than that, it's very hard for me to point you to anything more specific because those error messages are quite general. It would require a very close up investigation of your site.

akhter
User offline. Last seen 6 days 22 hours ago. Offline
Joined: 20/02/2010
Posts:
thanks

may be,

i am using custom template let me see

thanks for reply

ch
User offline. Last seen 6 weeks 6 days ago. Offline
Joined: 17/03/2010
Posts:
I get this too. Completely

I get this too. Completely vanilla install of version 0.31. Ran update.php and it didn't make any difference.

 

beng
User offline. Last seen 1 hour 50 min ago. Offline
Joined: 27/02/2009
Posts:
Oops. This is indeed a bug in ProsePoint itself. My apologies...

Oops. This is indeed a bug in ProsePoint itself. My apologies.

@akhtar: Sorry for doubting you in the first place. Since you had just upgraded to 0.31 and didn't run update.php, that was naturally the suspected cause.

@ch: Thanks for pointing this out. It made me take a second look which led me further.

Anyway ...

You can safely ignore the warning messages. They only occur on the .../admin/content/node-type/*/fields pages for content types which have a Workflow defined.

There is a fix which will be incorporated into future releases of ProsePoint.

However, if the issue annoys you enough and you'd like to patch your own system to fix it, then please do the following:

Edit the file .../profiles/prosepoint/modules/workflow_state/workflow_state.module on your site and delete lines 3 to 19 inclusive which say:

/**
* Implementation of hook_content_extra_fields.
*
* Inform CCK about this pseudo-field
*/
function workflow_state_content_extra_fields($type_name) {
  $extra = array();
  $wid = workflow_get_workflow_for_type($type_name);
  if ($wid) {
    $extra['workflow'] = array(
      'label' => check_plain(workflow_get_name($wid)),
      'description' => t('Workflow state form.'),
      'weight' => 0,
    );
  }
  return $extra;
}

In other words, remove this function entirely.

There was a recent update elsewhere in the code which made this a redundant function which clashed with something else.

Thank you.