Philtone

fabienhugues, if you’r using Pro Theme: that caused the issue. They released a fix today.

• This reply was modified 1 year, 11 months ago by Philtone.

I have the same issue on all my Sites that have auto-updated to 6.2 and I can’t figure out why this happened. Some almost have no plugins installed and still don’t work

If possible I would suggest reinstalling wordpress – my second configuration was on the same server with the same settings and there it worked.

Hey mark, I decided to use another plugin since the customer needed his website done.

I tested it on another configuration some days ago and it worked without a problem so i guess it was some wordpress “thing”

To answer your question: In the backend it said that it saved but the settings weren’t saved. Not in the backed or the frontend.

Hey Mark,

I tried everything here without success ..

I have made some tests to check whats not working on saving.

$input is returning this array:
Array ( [show_photos] => 1 [photo_label] => Photo [show_number] => 1 [number_label] => Nbr [name_label] => Name [show_position] => 1 [position_label] => Pos [show_height] => 1 [height_label] => Ht [show_weight] => 1 [weight_label] => Wt [show_year] => 0 [year_label] => Year [show_experience] => 0 [experience_label] => Exp [show_age] => 0 [age_label] => Age [show_home_town] => 0 [home_town_label] => Home Town [show_last_school] => 0 [last_school_label] => Last School [show_country] => 0 [country_label] => Country [show_bats_throws] => 0 [bats_throws_label] => Bat/Thw [show_other_info] => 0 [other_info_label] => Other )

while $output gives me this result:
O

I believe that output is exactly the problem of why the plugin is not saving, any insight on what could be wrong?

Ok, thx Mark!

Heya,

thx for replying!

I have already tried to deactivate everything, but that didn’t help..

I am using:

– WordPress 4.9.4
– MSTW Team Rosters Version 4.1.2
– Running PHP version: 5.6.33

My debug log shows me the following:

[05-Mar-2018 07:40:21 UTC] PHP Warning: array_key_exists() expects parameter 2 to be array, string given in …../wp-content/plugins/team-rosters/includes/mstw-tr-settings.php on line 237

and then several logs like this:

[05-Mar-2018 07:40:21 UTC] PHP Warning: Illegal string offset ‘show_photos’ in …../wp-content/plugins/team-rosters/includes/mstw-tr-settings.php on line 283

and:

[05-Mar-2018 07:40:21 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at …../wp-content/plugins/team-rosters/includes/mstw-tr-settings.php:237) in …../wp-includes/pluggable.php on line 1216

I just saw that it’s actually about the field “billing_state” wich isn’t even showing up in my form.

I have deactivated it in the functions.php and now it works

Ehm i’m not quite sure if my problem is the same because i don’t have the condition in a condition.

I’ve tried this:

<p>W?hle deinen Ansprechpartner
[select* your-recipient "KNRD Fest booking|[email protected]"
                    "KNRD Gigs booking|[email protected]"
                    "Press|[email protected]"
                    "Allgemein|[email protected]"]
 </p>
[group probe]

<p>H?rprobe
[url Hoerprobe placeholder "Type Link - for example: https://bandcamp..."]
</p>

[/group]

Now when I place the form in the visual editor I already see, that “[/group]” is being shown as code – but i shouldn’t be seeing any code there wich tells me that something is going wrong here.

So as i already assumed, the condition also isn’t working, when i save and look at the real page.

Could you help me here?

Thx in advance,
Phil

never mind – i just deactivated and reactivated the plugin. now it works again ..

basically, to make it less complicated:

it doesn’t save anything ??

yup, then the page reloads and everything is as before i changed it ..

Thx for the quick reply! looking forward to the future release – this plugin is pretty awesome ??

never mind – it was a plugin wich messed the code up

Hey – i’ve solved it in buying the pro version. It updated the info via “ajax” and doesn’t have to reaload the page wich causes the problem..