Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given - theme_get_registry() (eilutė 277 iš /data/disk/o1/static/platforms/d7/includes/theme.inc).
    Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given - theme_get_registry() (eilutė 277 iš /data/disk/o1/static/platforms/d7/includes/theme.inc).
    Warning: call_user_func_array() expects parameter 1 to be a valid callback, no array or string given - theme_get_registry() (eilutė 277 iš /data/disk/o1/static/platforms/d7/includes/theme.inc).

Appears on every action which clears cache or also some others.

Getting this when working with custom payment module, which extends Commerce. Have no idea why this is happening, because on Bartic it is ok.

Sky and AT are latest dev

How may payment processor (local payment company with their module) do smth with this???

Comments

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented
Category: Bug report » Support request

Not yet established as a bug, please provide more details so we can establish that.

I mean show me how to reproduce it, strait off I can't, so either we close it as cannot reproduce or we need an explanation/details of the actual bug.

Its clear whats going on from the message, but as to why?

PlayfulWolf’s picture

PlayfulWolf CreditAttribution: PlayfulWolf commented

Ok, no prob.
To replicate:
1. Drupal (using 7.23, but I do not think this is core related), Sky latest 3.dev. Using BOA install, Display suite, Context, Views, Entity cache enabled no other exotic modules. Most of the modules are either stable releases or last dev which are confirmed to work.
2. Last link of: https://support.paysera.com/index.php?/Knowledgebase/Article/View/103/37... . Also all required *commerce modules for its installation
3. Clean cache - the warning will appear on any Sky page when caches are cleared. It seems not to show in AT admin.

The thing is that everything works fine in Bartik.

I contacted with this issue that custom module developer, they are also looking at the issue.

PlayfulWolf’s picture

PlayfulWolf CreditAttribution: PlayfulWolf commented
Category: Support request » Bug report
Priority: Normal » Minor

I am marking this as bug, as this is Sky related as with the latest 7.3dev Pixture_reloaded no such error. Have no idea what is causing this. Even tried to disable modules in bunches - only combination of that custom module and Sky is making those warnings appear.

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented
Category: Bug report » Support request
Priority: Minor » Normal

Well, you would need to make available a full copy of your site, there is no way I can ever hope of replicating your configuration.

This does not show a bug, only a correlation, you cannot infer causality from a single correlative event. Sorry but as yet we have not determined the source of the issue.

PlayfulWolf’s picture

PlayfulWolf CreditAttribution: PlayfulWolf commented

I am using Pixture Reloaded as a base for custom theme then. It works well. Will it get the same attention of yours as Sky?

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

He he, maybe, whats happening is all the sub themes are getting updated and upgraded, bug fixed and spruced up, so I am paying plenty of attention to the issue queues right now, once they are released as new versions I will likely go back into my cave for a while and only respond to serious bug reports etc.

I'm taking this one seriously, trust me, but it's really really hard for me to reproduce, mainly due the time involved in trying to do so.

J-o-h-n’s picture

J-o-h-n CreditAttribution: J-o-h-n commented

I guarantee to get this error whenever the site runs the checks for any new versions of the modules installed. Whenever this cronjob is running in the background this error will appear.