I updated DWQA to the latest version 22.214.171.124 and I now have a problem with the custom post types "Question" and "Answer".
I am using the third-party plugin Linkpatrol to strip unwanted URLs.
Until version 1.3.6 linkpatrol worked perfectly for the custom post types "Question" and "Answer".
Since version 126.96.36.199, it doesn’t work at all for questions and answers.
For example, on this question, the Plaisio.gr URL should have been stripped by linkpatrol.
This is extremely important, because since DWQA is lacking any automated way to handle URLs (strip them or add the nofollow attribute), linkpatrol was the only way to manage my readers’ links.
In DWQA version 188.8.131.52, I have added auto function which converts plain-text URL to HTML links. Currently, on our DesignWall also encountered the same situation as you, and we have conducted additional attribute
target=”_blank” in all the links. This help us avoid spam links. If this solutions better than using plugins, I will consider to add this feature into upcoming version of DWQA.
Hi Kevin, thank you for your answer.
The automated ref="nofollow" and target="_blank" attributes are essential for user-submitted content, you should definitely add this feature.
What would also be great, though, is if we had the option to block any URLs posted by non-staff users. Can you add such an option in the upcoming version? With a setting to activate it or deactivate it on the Settings screen.
Hi Angelos Kyritsis,
I will consider to add this feature into an upcoming version of DWQA.
There are more problems with the custom posts, that I just found out.
I used to be injecting ads between the question title and the question, and between the question and the answer, and now this injection is impossible.
I am forced to revert to version 1.3.6, please make sure to "un-break" the custom post type in future versions, because it has destroyed a huge part of the Q&A functionality for my website, and I guess for other user’s too.
Hi Angelos Kyritsis,
I’m checking it and you’ll have it fixed in the DWQA’s upcoming version.
Please login or Register to submit your answer