Error Notice with WooTickets

[Vicky]

Hello,

I get the following warning message whenever I save an item in the Menu area.
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ‘TribeWooTickets::handle_delete_product’ was given in /wp-includes/plugin.php on line 406
Not sure if this related, but I also have issues when I add a new event. The dropdown menu items (e.g. Venue Name, Country, State or Province, Organizer Name, etc) are all opened and don’t close.

[Barry]

Hi Vicky,

I believe I can see the problem in the source code – even so it would be great if you could confirm step-by-step what you are doing when you see this?

[Sean Mulkerrin]

I get the same problem.

[Barry]

Hi Noel,

Though we’ve got a possible bead on this already we can’t actually replicate the problem – can I ask you to provide some details of the steps you are running through when you see this?

That would be much appreciated.

[hallahund]

Hi there…

I get the exact same warning: “Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ‘TribeWooTickets::handle_delete_product’ was given in /storage/content/01/159001/hallahund.se/public_html/wp-includes/plugin.php on line 406”

I also (after latest update from you) get this “Unable to save…” message from WP (it’s in the red frame on the screen dump on the link below. The WP Message is in Swedish, but it basically says: “The connection was lost. The ability to save has been disabled until you are connected again. We take a backup of this post in your browser, to be on the safe side.”
Skitch = https://www.evernote.com/shard/s48/sh/a5ebadac-66b1-40df-a427-e621ecd092c6/20b28274d736c0d195552cd50deb1b4b

It appears to send warning randomly, since it shows both on post and pages, but if you click on the post/page again it has disappeared – to show on another post/page (which in most cases it didn’t show earlier.

Conclusion = it is not assigned to any specific areas of post/pages, but shows on “all of them”.

====

What I’ve tried so far is…
– Runned the site with ALL plug-ins deactivated
– Had a conversation with my host (Binero.se) about chmod’s and stuff – but they can’t find anything wrong
– Re-installed WordPress 3.6

Problem still remains.

// M.

[hallahund]

Additional info:

I’ve spoken to my web-host, and they say (according to what thet find by check you Plug-In “WooTickets”) that it requires a full read/write on several files in the WP-installation (CHMOD 777). Something (quote) “…we are not quite comfortable with…” 🙂

All of these issues appeared after your latest update. Is there something not right here?

// Mn.

[Barry]

Hi everyone, so a possible short term fix would be to follow the instructions in the following post: https://theeventscalendar.com/support/forums/topic/errors-appearing-when-editing-menus/#post-59937

Alternatively, if you aren’t comfortable with that (since it involves editing core plugin code I appreciate not everyone will be) then please note that our next maintenance release should resolve this issue.

I’ve spoken to my web-host, and they say (according to what thet find by check you Plug-In “WooTickets”) that it requires a full read/write on several files in the WP-installation (CHMOD 777). Something (quote) “…we are not quite comfortable with…”

That sounds like a quite separate issue, but there isn’t really enough information to go on here.

We’d really need to know what they are referring to when they refer to several files in the WP-installation – do they mean core WordPress files? Files within the designated upload directory? I would also note that my test site does not have such a permissive file access level and works just fine.

So we would definitely be happy to look into this in more detail if it’s a concern for you – but please create a new thread and if possible provide some further information as outlined above.

[hallahund]

Hi Barry, and thank you. I used your php-coding solution and it seems to work fine. Looking forward to the next update but problem solved for now.

Regarding the message from my web-host, I’ll continue the dialogue with them, since I’m still convinced my other problem is a hosting issue. The conversation I have with them is in Swedish, so it’s hard to translate exactly, but what he wrote was:

“What WooTickets require is something I am not entirely comfortable with, since full read/write rights on files – on a public site – is not to be recommended from a safety standpoint.”

I have pointed out to him that I’m not quite sure what he means by that, so I won’t bother this forum with their issues. If he still insists it’s something to do with the plug-in, I’ll get back to you with a more complete description.

Bye for now!

// Mn.

[Barry]

Definitely – we would be happy to investigate if there is a legitimate issue here, however right now I can’t think what that would be.

Our own testing and demo sites run WooCommerce Tickets (“WooTickets”) successfully without having permissions at that level – similarly my local test installation has no problems when locked down quite tightly.

It may be that in your particular hosting environment this is necessary to workaround some other problem, if so it would really be something for the host to resolve – though once again we’re completely open to looking into this if they can provide notes that suggest a wider problem.

Thanks for your patience and yes, feel free to check in if you need to with any further feedback from the host.

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts