WAP Support

It could be something with your wp-config.php file. Please open it add check if ABSPATH i defined correctly, example:

* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

You could also check the permissions of the file, make sure it’s 755.

That’s a good idea for new AGCA feature. It does not exist right now, but it’s very good candidate for one of the next releases.

A quick idea could be that you add a JS in AGCA advanced window that redirects user from Dashboard page to a page of your choice. It could do the following:
– Checks if current page is Dashboard page (check if url is equal to “<yoursite>/wp-admin/”)
– If it is, redirect it to a new page (of your choice)

You will still be able to manually access Dashboard page, via admin menu, since it has slightly different url “/wp-admin/index.php”

This is not a perfect way to implement this, since it should be done in backround, but it could work in your case as a workaround.

Thanks,
WAP support

Hi Elan,

Please try setting AGCA folder permissions recursively to 755. Othe than that, Sucuri might be a reason. You can check that easily just if you disable it temporary.

If you need other ideas, please have a look at this link
https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-403-forbidden-error-in-wordpress/

Thanks!

Thanks for the feedback, we will make this easier in the next releases.

Basically, you need to choose capability on General page to separate AGCA administrators (can be any user with the selected capability) from other users. Other users will be affected by customizations. If you want to further secure AGCA, there is a code snippet in previous questions that you can use to password protect AGCA settings page.

Thanks!

Resolved in AGCA 5.7

Marked as resolved, since there’s no additional response from user.

Marked as resolved, since there’s not additional response from user.

Marked as resolved, since there’s no response from user

Marking this issue as resolved, since there are no further replies.

Hi,

Thanks for your feedback. Admin bar on public front end is not supported by AGCA since it does not appear by default in WordPress. Could you please also check if your theme enables it? We should know first how it’s enabled in order to add support for it. If you can investigate this a bit, that would be really helpful!

To force disabling it, you could try adding this in your theme’s functions.php:

function show_public_admin_bar($bool) {
	if(!is_user_logged_in()){
		return false;
	}
	return true;
}
add_filter('show_admin_bar', 'show_public_admin_bar');

Try also adding a higher priority if there’s a similar function somewhere that does the same:

add_filter('show_admin_bar', 'show_public_admin_bar', 999);

Kind regards
WAP support

Hi,

Admin bar should not show up publically by default. Please check if there’s some other plugin that does that.

There’s an option in AGCA: Site pages: Admin bar customizations, that can be used to prevent AGCA customizations from site pages. Hope this helps.

Kind regards
WAP support

This is a nice catch, thanks for reporting!

Hi,

Everything should be the same, except the resources like images that are used in the configuration. You should go ahead and manually change the URLs of images to point to the new domain.

Good luck,
WAP support

Hi,

Thanks for the update. Please do the following:
– open ag-custom-admin/plugin.php
– go to line 922, you will see this:

if(get_option('agca_admin_bar_frontend')!=true && is_user_logged_in()){

Replace it with this line:

if(get_option('agca_admin_bar_frontend')!=true){

Please let us know if this solves your problem.

Thanks,
WAP support

• This reply was modified 8 years, 5 months ago by WAP Support.

Thank you so much! We really appreciate your support and hope you’ll keep using AGCA in future!