Support Forum
Hi:
I think that security warning is a clue. Is your site running https? If so, maybe make sure that all the items on the page is also being served via https:.
Other than that, there might be some sort of conflict with the theme or an existing plugin. Some additional things to check on or try:
1. Turn off COMBINED CACHING option under FORUM->OPTIONS->GLOBAL SETTINGS.
2. Open up your browser console and see if there are any javascript errors being shown in there.
3. Switch your WordPress theme to one of the core 2017/18/19 theme, clear your caches (if you or your host have any turned on) and see if the text shows up.
4. Go to FORUM->TOOLBOX->ERROR LOG and clear the log. Then try viewing the forum again and see if any new errors show up in that log.
5. Check your WordPress debug.log file to see if there are any errors being thrown in there. (You might need to turn on your WordPress debug flags first).
You can do all of these things individually – they’re not dependent on each other. I just listed them in the order of easiest to hardest.
Thanks.
1. Never was on.
2. Shows:
JQMIGRATE: Migrate is installed, version 1.4.1 jquery-migrate.min.js:2:542
onmozfullscreenchange is deprecated. jquery.js:2:1539
onmozfullscreenerror is deprecated. jquery.js:2:1539
3. I’m on 2017. I activated 2019, and that changed nothing. I changed it back.
4. There are no Error Log Entries
5. There is nothing in the debug.log, even turned on.
I came across this post whilst trying to solve a similar problem - I could not edit posts, only reply to them.
After a lot of debugging, I found the solution. Maybe it will help others.
I am using the iThemes Security Pro plug-in the redirect non-SSL URLs to their SSL versions, which normally works well and I have one other SimplePress site using this configuration without any problems.
But for the affected site, SimplePress was not recognising the permalink and showing the http: version in the "Integration" section. Even the manuall "Update Forum Permalink" did not solve this problem, so in the end I took a brave (and backed-up) plunge into the "sfoptions" table and the "sfpermalink" record by hand.
Problem solved!
1 Guest(s)