|
Teodor Nedelchev
|
January 24, 2013 at 1:55 pm
Dear Sirs,
The following error occurred by me:
Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/namag/public_html/workshop.bg/wp-includes/post.php on line 2996
When I turn-off the plug-in Event Espresso this error disappears. Another very big problem, which exists, is that the plug-in can not make any corrections on its options. The fields Contact Information and Page Settings, after choosing whatever option from them, they don’t change the information. This is a very serious problem for me, because I can’t use your plug-in.
|
|
Jonathan Wilson
|
January 24, 2013 at 4:52 pm
Hello Teodor,
Try to rule out any plugin conflicts. Deactivate all non Event Espresso plugins and test to see if the issue is still occurring. If it is not, then we know it is a problem with another plugin. You can then find out which plugin it is by reactivating each plugin individually and testing to see if the problem starts happening after the activation. When it occurs after activating a plugin, then we know this is the culprit.
|
|
Teodor Nedelchev
|
January 24, 2013 at 11:36 pm
I don’t have any other plugins different from Event Espresso. I have only Premium Theme – Press Event. When I deactivate Event Espresso the problem dissappears. I don’t have what else to do.
|
|
Josh
|
January 25, 2013 at 12:56 pm
Hi Teodor,
Where are you seeing the array_merge error, and what steps would I need to do to reproduce it?
With the General Settings not saving, can you check to see if that happens if you switch to another theme?
Also, is this a multi site installation of WordPress, or a single site?
|
|
Teodor Nedelchev
|
January 25, 2013 at 1:33 pm
Hi,
The plug-in does not allow the saving of whatever information part of the General Settings with the use of different themes and there constantly appears the symbol “$”. It was impossible to change the Page Settings.
It was obtained with the different themes. As I couldn’t wait your reply I decided to delete everything and started again … I hope this problem would occur never again.
|
|
Josh
|
January 25, 2013 at 3:32 pm
Hi Teodor,
So now that you’ve reinstalled, it’s not happening anymore?
|
