First of all, I never called out anything, I’m just relating a fact : I’m not the only one having this issue on the forum and even on stackoverflow, that’s a fact.
Secondly, I never said wordpress was good for my usecase, I said, saying wordpress sucks while it powers 33% is a bit silly, there are things that sucks in wordpress like there are things that sucks in any tool. I’m not specifically fan of wordpress and I’m not specifically fan of cockpit either, I use tools that are right for a certain task, and in my current case, a headless CMS was the right tool for me, not Wordpress.
That being said saying
tries to solve the same problem but from different angle
to justify the fact that absolute urls aren’t sent in the REST Api response is not a valid argument because, as I said : I’m not the only one having the issue, and the WYSIWYG type exists for a reason, and one issue with it is, having relative paths inside it while a headless CMS is supposed to be used from any environnement like a mobile app where it would be annoying to have to parse HTML generated by the WYSIWYG content to add the CMS’s domain url.
I don’t need plugins or themes or any kind os stuff like that, that’s why I don’t use Wordpress in the current situation, I used cockpit among many other option like Directus that could have done the trick, I just prefered cockpit’s docs & sqlite approach because I needed a small API, if the API was suppose to be big I would have used Directus or even Contentful for that matter.
You’re actually the one calling me out for the simple fact that I’m stating something obvious : if there’s a WYSIWYG field with image that can be inserted, and the the CMS’s API can be used on a mobile app or a different domain from the CMS, why can’t we have in the API response, the absolute path on image FOR THE WYSIWYG field.
My question is simple, the use-case is simple, I’m not calling out anyone but if that’s how cockpit’s community is (not accepting criticism and feedback), I guess i’ll just not use it next time.
By the way, if I really wanted to call out cockpit I would have called out all the other “absurde” things cockpit does and call REST while it isn’t RESTful at all. Oops, now I did.
Le mar. 8 oct. 2019 à 22:24, Blistok via Cockpit Community firstname.lastname@example.org a écrit :