bradallenfisher

this is much needed and would be amazing!

wait so what’s the point of the exclusion??? why have the “follow” dropdown in there?

I’m confused. Thanks!

That’s great. I actually had them open up a ticket for me, but since I was able to get it working by doing the export from local they gave up on it saying that it wasn’t an issue… so I’m glad that you’ve opened it backup.

Would you please do me a favor and update this ticket whenever they come up with a solution???that way I can stop using my work around.

Yes thank you but that didn’t fix it. I added the absolute path. The only thing that would make it work is if I built the site locally and then exported it up to cloudways. I have a feeling it has something to do with the way they’re using file system management. They’re using load balancers and probably some sort of NFS or file mount and I think it’s just getting mixed up when it’s trying to look for the json file.

Thank you yes I have actually tracked this down to be specific to cloudways hosting platform. I can’t replicate the issue on my vagrant or linode environments either. I have put in a ticket with them but the problem is when I build the site on my local and import it I can’t replicate it that way either. It’s only when I create the site on the cloudways hosting platform that I have any issue.

Since this is such an edge case, I’m going to just close this request.

This is what is coming back in inspector. There are about 37 of these types of notices… not sure if it’s breaking js from loading the templates or what.

blocks.min.js?ver=e2b6602c7ebbe8ce93832ce35d81be1c:2

The block “geodirectory/geodir-widget-search” is registered with an invalid category “geodirectory”.