WPIntell

Source evidence

Problem with bedrock installation

Wp Social Login and Register Social Counter · support · 2025-01-28T13:26:00+00:00

mixedsentiment
mediumseverity
0.72relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 25 rows with source links

24.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Chiara Aiola resolved
Hello, Your plugin doesn’t work with the bedrock stack, because the function get_site_url() returns the home url with the /wp path appended (see https://discourse.roots.io/t/site-url-returning-wp/12270 ). For this reason, every time that the function is used in the plugin to create the url to the wp-json path it returns www.mydomain.com/wp/wp-json/wslu-social-login/ An alternative could be to use get_home_url instead. Dear @aiolawp , Thanks for reaching out to us. I understand your concern and have forwarded the issue and suggestion to the development team for further investigation. They are currently looking into it. I will keep you updated as soon as I receive any feedback from them. Your patience and cooperation in this matter are greatly appreciated. Best Regards, Reju Dear @reedwanul , thank you for your answer and I hope the development team can fix this issue. Temporarly I solved my problem using this workaround: added this rule to .htaccess RewriteRule ^wp/wp-json/(.*) /wp-json/$1 [R=301,L] In this way I can redirect all the traffic to the wrong address to the correct one. Thank you, CHiara Dear @aiolawp , I hope you’re doing well! I’m glad to hear you found a temporary solution. Our dev team is still working on this issue, and once it’s fixed and passes QA, we’ll release a new version. Stay tuned for updates! Best Regards, Reju Dear @aiolawp , I hope you are doing well, and I’m glad to inform you that the issue has been fixed with the official release of a new version. Please update to the latest version. Your patience and cooperation throughout this process are greatly appreciated. Feel free to let me know if you have any other questions or need clarification. Best Regards, Reju

Comments

4 shown
Reedwanul Haque 2025-01-30T04:59:00+00:00

Dear @aiolawp , Thanks for reaching out to us. I understand your concern and have forwarded the issue and suggestion to the development team for further investigation. They are currently looking into it. I will keep you updated as soon as I receive any feedback from them. Your patience and cooperation in this matter are greatly appreciated. Best Regards, Reju

Chiara Aiola 2025-01-30T07:51:00+00:00

Dear @reedwanul , thank you for your answer and I hope the development team can fix this issue. Temporarly I solved my problem using this workaround: added this rule to .htaccess RewriteRule ^wp/wp-json/(.*) /wp-json/$1 [R=301,L] In this way I can redirect all the traffic to the wrong address to the correct one. Thank you, CHiara

Reedwanul Haque 2025-02-01T07:49:00+00:00

Dear @aiolawp , I hope you’re doing well! I’m glad to hear you found a temporary solution. Our dev team is still working on this issue, and once it’s fixed and passes QA, we’ll release a new version. Stay tuned for updates! Best Regards, Reju

Reedwanul Haque 2025-02-10T05:40:00+00:00

Dear @aiolawp , I hope you are doing well, and I’m glad to inform you that the issue has been fixed with the official release of a new version. Please update to the latest version. Your patience and cooperation throughout this process are greatly appreciated. Feel free to let me know if you have any other questions or need clarification. Best Regards, Reju