Notice: This forum has become difficult to maintain and will no longer be supported.
If you have a current account or a bug report, please open a ticket. If you have questions about the free version of Business Directory, please post in the WordPress.org forum and our team will respond there.
First, thank you for your work on this plugin. The last update causes all kinds of out of memory issues in the backend. Granted all of the new features are great, but not at the cost of having other features inaccessible, due to the out of memory issues.
It maybe the cause of any problems that users are having after the last update.
Out of memory issues usually mean that your server is underpowered. The plugin itself doesn't consume a huge amount of memory (nothing from the last update is memory intensive) and on a reasonably configured server, it performs as expected.
WordPress in general is pretty memory intensive, so if you install a bunch of plugins and use an image-heavy theme, that will require some server resources to hand it all to the client. If you have a busy server on top of that, out of memory issues will occur frequently.
I see this most often on shared hosting plans. You might consider a different plan, a VPS, or moving to a different shared host. Any of those may fix the problem, but it's not specific to BD I'm afraid.
Thanks for the reply wpbdm. This is currently being used on a developers server where I'm alloted 256mb of ram. Usually I get this when I have conflicts with other plugins or a plugin is not coded efficiently/correctly. I've deactivated another plugin and has helped.
I guess I'm more curious to know if this plugin has any known conflicts with other plugins.
There aren't any known conflicts anymore (we had one with Yoast, but fixed it in 2.0.3 because it's such an important plugin). If you find one, let me know.
Most Users Ever Online: 402
Currently Browsing this Page:
Guest Posters: 5349
Newest Members:Jess Willis
Moderators: bizdirectorysupport: 18712, BD Support: 3
Administrators: Business Directory Support: 1720, Steph Wells: 0