see a wp_sferrorlog??? well, of course the db table will still exist.. and with error logging back on, any notices, warnings and errors would still accumulate…
but the site now works with the error log back on?? odd… not what I expected… 
and now cannot debug the original issue…
i see only the error in the most users online
no big deal (i changed it in db manual setting value 1 and now it counts again!)
but i worry if i found some other errors later
till now everything seems ok
apart from every new user takes the –testuser– instead of testuser as a display name…..
are you saying your are getting — around a user name?? what settings do you have on forum – profile – profile settings for display name? keep in mind that you cannot have duplicate display names…
this looks like some debug code that might have gotten left in the code by accident on the last release…
in file simple-press/sp-api/sp-api-users.php, around line 614, change
return ‘–‘.$modname.’–‘;
to
return $modname;
to resolve… need to do some more testing, but may want to release an update to handle this…
there was a notice for updating to 10781
i did it and now everything is ok! no — —
after the update i performed the db upgrade with no errors but in the error log there was some notices
file: s/simple-press/forum/content/forms/sp-form-components.php
line: 139
function: sp_post_editor_submit_buttons
Notice | Undefined variable: tipCancelButton
also after the upgradre i clicked at the option ” Go to forum admin”(something like that) and it told me that i dont have the permissions.
i refreshed and then everything ok…
yes, the latest 5.3.4 release fixes the dashes around names… It wont retroactive fix users it affected, but stops doing it…
so i think we are ok now!!
thank you Mr Papa.
i will post on the unified forum another issue irrelevant with this.
sorry to open the topic again but i found what was the problem
when i tried to update i had installed DB Cache reloaded fix
that caused the errors!
today i installed it again and forum was down messing the whole site
i deactivated simple press and everything is ok again
this plugin breaks simple press!
yes, of course… we have said many, many times that you cannot cache the wp page the forum is on. All forum content appears on a single wp page, so its dynamic in nature and cannot be cached by plugins that treat it as a static page.
Actually Db caches database query’s, but after the last simple press update there was the problem
I will exclude simple press tables from caching!
Also i use WP fastest cache which actually caches every forum topic creating an index.html for everyone of them!
Its the first plugin that did that for me and i am surprised but it works!
Thank u Mr Papa!
nothing would have changed regarding db caching… it still associates it with a page, so problematic…
WP fastest cache, eh? interesting, that means it would be a caching plugin that is actually looking at the canonical url instead of the wp page… might have to look at it some day… thanks!