bstnstn
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Raft] Shortcodes not working on Raft front page?Hi @luciamarinescu, thanks for your reply!
I found out that the Shortcode works if I move it out of the “startpage template” area (as indicated by the Gutenberg breadcrumbs on the bottom), and instead insert it somewhere outside, for example on the “page” level of the breadcrumbs, above or below the “startpage template” part.
I also had problems that the shortcode block wasn’t working when inside a Gutenberg group, until I converted it to a Gutenberg HTML block.
I hope this information helps anyone else who might be encountering this problem.
Best,
bstnstnHi @takayukister, thanks for your quick reply!
I have now debugged the problem. It’s possible there was a caching issue on the project’s server that caused the form to not correctly display the select field when I added the blank option.
On a related note, I noticed that some fonts will cause problems with the content of the blank option, i.e. the three minus symbols
---:The font on this customer’s site was automatically converting double minus to an em dash, resulting in a broken display of the characters that was very noticeable in some browsers:
—-.I’m not sure if this was connected to the problems that I had encountered. I had to change the font.
In any case, it might be advisable to perhaps only use a single minus “-” here, or make it possible to change the content of the blank option.
Hi @rafinkhan,
thanks for your answer. It seems like I found the culprit for the problem in the .htaccess of the page.
I found the problem after reading that some people solved a similar REST error after updating their .htaccess (via Settings->Permalinks->Save). That alone did not solve it for my page, but there was something else in the .htaccess that blocked REST, i.e. an older .htaccess-only-based firewall solution installed by a former developer, something I had not encountered before.
After removing it, the plugin works again as intended! Strange, that it worked without problems before, until the core update of WP.The problematic .htaccess settings seemed to have been based on this open source git: https://gist.github.com/lucasjahn/758092e75a8aa01e63c2
After removing the “6G Firewall” block, the problem disappeared.Hi @rafinkhan,
thanks for the quick answer. I just tried that, but the problem persists. I also tried different browsers (Chrome, Safari) and deactivating/reactivating/re-installing the plugin. Sadly, none of it helped.