Title: Plugin Using Outdated Codex Last modified: August 28, 2019 --- # Plugin Using Outdated Codex * [duchesscorp](https://wordpress.org/support/users/duchesscorp/) * (@duchesscorp) * [7 years, 3 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/) * We tried this plugin in a test environment and it was considerably buggy but we made a few workarounds. When we finally went live, the error log was bananas and it completely shut down areas of our client’s site. For the amount we paid for the pro version of this plugin, there’s no way we should have to create so many workarounds to get this thing to work. The errors were mostly related to outdated code and the plugin did not work well with WP 5.0. Reached out for a refund and the developer is holding our money hostage. If you must use, use this free one because the pro version is junk. * Update: * I’ve updated my initial rating for a 4. There are significantly more support options as well as improvements to the plugin since I initially tried it and the creator has provided additional customer service, plus we were able to get our refund on the pro plugin. I appreciate the creator’s willingness to work through the issues for a resolution. - This topic was modified 6 years, 9 months ago by [duchesscorp](https://wordpress.org/support/users/duchesscorp/). Reason: Updated support provided by creator Viewing 8 replies - 1 through 8 (of 8 total) * [stefanpieter](https://wordpress.org/support/users/stefanpieter/) * (@stefanpieter) * [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11863932) * [@duchesscorp](https://wordpress.org/support/users/duchesscorp/) are you still having these issues? * Have they managed to fix all the bugs you reported and how quick? * Plugin Author [Jose Vega](https://wordpress.org/support/users/josevega/) * (@josevega) * [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11863956) * Hi [@stefanpieter](https://wordpress.org/support/users/stefanpieter/). * Thank you for your interest in the plugin. I’m the author. * The user who posted the review is no longer using the plugin. * Currently, the plugin receives frequent updates, it’s well tested with the latest version of WordPress, WooCommerce, and popular plugins. You can see the [changelog here](https://wpfrontendadmin.com/changelog/). * It was last updated this week. - This reply was modified 6 years, 9 months ago by [Jose Vega](https://wordpress.org/support/users/josevega/). - This reply was modified 6 years, 9 months ago by [Jose Vega](https://wordpress.org/support/users/josevega/). * [stefanpieter](https://wordpress.org/support/users/stefanpieter/) * (@stefanpieter) * [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11863965) * That is great. * Will ask a few questions in the support section to make it visible. * Plugin Author [Jose Vega](https://wordpress.org/support/users/josevega/) * (@josevega) * [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11863970) * [@stefanpieter](https://wordpress.org/support/users/stefanpieter/) We have a live chat on [our website](https://wpfrontendadmin.com), I can answer all your questions there quickly. * Thread Starter [duchesscorp](https://wordpress.org/support/users/duchesscorp/) * (@duchesscorp) * [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11864399) * We discontinued using the buggy plugin when we couldn’t get it to work. We lost a major client and the plugin creator kept our $400. This plugin cost us a few thousand dollars in losses and all we have to show for it is a license key we don’t want. If it’s fixed now, great but that doesn’t retrieve the money we lost back. * [stefanpieter](https://wordpress.org/support/users/stefanpieter/) * (@stefanpieter) * [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11864410) * [@duchesscorp](https://wordpress.org/support/users/duchesscorp/) thank you for responding. * What function of the plugin did not work or was limited that caused you not to find it a viable option? * Thread Starter [duchesscorp](https://wordpress.org/support/users/duchesscorp/) * (@duchesscorp) * [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11864414) * At the time, the outdated codex was the issue. We were using the plugin with Ultimate Member and addons. Pages would show up with white screens like the user was not supposed to have access to the page even though they were an administrator. Beaver Builder pages and Gutenberg pages showed up with content blocks doubled so it looked like we built a page within a page. The plugin was not compatible with WP 5.0 at all. Javascript on certain pages was render blocking and the log would trace back to code within the plugin. We tried a few php and functions workarounds to try to get it to work but fixing one issue just caused others. The plugin seemed to work fine in a local environment. There were all kinds of issues when we went live. We never did find a solution that would bring the admin on the front end so we tried to result to admin menus for the issue but the client was upset that their live site drastically lost function on a site that has a distinct day and time for release. We lost a lot of money on this plugin. * Plugin Author [Jose Vega](https://wordpress.org/support/users/josevega/) * (@josevega) * [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11869560) * Thank you for sharing your experience. * I want to share some facts for future readers. * – We provide great customer support every day We have the live chat on our website, contact form, support form in wp-admin, and wp.org’s forum. * Everything is answered on the same day, sometimes in a matter of minutes. * – We have a simple refund policy. Free trial for 7 days + 14 days of money-back guarantee = 21 days of full protection. * – The plugin is well tested, it receives frequent updates, and it’s used by more than 900 web apps and multisite networks. * – We never received a support ticket asking for help for those specific issues. If we had received a support message when those issues happened, all those problems could have been avoided if we were given the opportunity to help. * I encourage future users to try the plugin and don’t hesitate to request support, we’re one chat message away. Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘Plugin Using Outdated Codex’ is closed to new replies. * ![](https://ps.w.org/display-admin-page-on-frontend/assets/icon-256x256.png?rev =1989717) * [WP Frontend Admin - Display WP Admin Pages in the Frontend](https://wordpress.org/plugins/display-admin-page-on-frontend/) * [Support Threads](https://wordpress.org/support/plugin/display-admin-page-on-frontend/) * [Active Topics](https://wordpress.org/support/plugin/display-admin-page-on-frontend/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/display-admin-page-on-frontend/unresolved/) * [Reviews](https://wordpress.org/support/plugin/display-admin-page-on-frontend/reviews/) * 8 replies * 3 participants * Last reply from: [Jose Vega](https://wordpress.org/support/users/josevega/) * Last activity: [6 years, 9 months ago](https://wordpress.org/support/topic/plugin-using-outdated-codex/#post-11869560)