stephenhaiman
Forum Replies Created
-
thank you for your prompt response. Much appreciated. I am delighted with the performance of the plug-in and the add-ons that I bought and everything is working perfectly. thank you for your prompt response. Much appreciated. I am delighted with the performance of the plug-in and the add-ons that I bought and everything is working perfectly.
the only thing I’d still like to change is for the mobile version for the picture and the email link to be above the body text so that everything is in one column. The presentation on tablet and on desktop is perfect. I don’t see a way to do that presently, is there any CSS I can use to do that?
I went ahead and installed it, and it works fine. I also bought the circled template and the custom order extension. All are working great. I would like on a mobile device (cell phone) to have the picture and email icon appear above the person’s name to give the whole entry more width. Basically I want for the mobile view everything to be in one column. Can you give me the CSS to do that please?
Problem resolved. There were 2 other plugins that were interfering with AIOWS and Pinpoint. AIOWS was not interfering with AIOWS when I deactivated all other plugins other than AIOWS and Pinpoint. The main culprit was the Woocommerce add on for shipping and tax. When I deactivated that plugin the problem went away. Interestingly enough that this problem wasn’t there in WP version 5.6.2. When I upgraded to version 5.7 I had multiple issues come up with 3 other older plugins. I upgraded the ones that are compatible with 5.7, and deleted 2 that were not compatible. I suspect that WP 5.7 upgrade will have affected numerous plugins for many sites. Your diagnostic recommendation was a good one. It allowed me to determine that AIOWS was not the issue after all, but rather a conflict between AIOWS and the older plugins that were actually interfering with Pinpoint and AIOWS.
Forum: Plugins
In reply to: [Autoptimize] autoptimize and siteorigin conflictThe error variable is cust_login, not cost_login.
Forum: Plugins
In reply to: [Autoptimize] autoptimize and siteorigin conflictFound where the error is occurring. When I look at the error information on inspecting the page in chrome, I get the following error:
SyntaxError: Can’t create duplicate variable: ‘cost_login’
(anonymous function) – site origin-panels.min.js:1:29553When I disable woo commerce and autoptimize is enabled no error
When I enable woo commerce and disable autoptimize no error
When I enable woo commerce and enable autoptimize get 404 error in site origin
When I enable woocommerce and autoptimize get error.I can send you an image of error console if that would help. Don’t think I can do that however through this forum. Don’t see the ability to upload a file in this forum.
Forum: Plugins
In reply to: [Autoptimize] autoptimize and siteorigin conflictI am not sure I have access to the PHP error log. I am on the GoDaddy cPanel, but unsure where to find the error log. Should I have access to it, and if so can you point me to where the file would be located?
Forum: Plugins
In reply to: [Autoptimize] autoptimize and siteorigin conflictI did that and still get a 404 error in the SiteOrigin Editor. 404 error goes away when I disable autoptimize. Tried disabling all the other plugins other than autoptimize and found out that there is a conflict with the Woocommerce plugin. When I disable just that plugin the problem goes away, even when I enable everything in autoptimize. There obviously then is a conflict between autoptimize, woocommerce, and site origin. The problem goes away when I have all my plugins activated except woo commerce.
Forum: Fixing WordPress
In reply to: buddypress you do not have sufficient permissions errorI found a solution, but I’m not sure it is the right one. I changed the following in the buddy press community stats > admin > bp-community-stats-admin.php file.
For the form post it was set to:
<form action=”<?php echo network_admin_url(‘/admin.php?page=bp-community-stats-settings’); ?>” name=”bp-community-stats-settings-form” id=”bp-community-stats-settings-form” method=”post”>
I changed it to:
<form action=”options-general.php?page=bp-community-stats-settings” name=”bp-community-stats-settings-form” id=”bp-community-stats-settings-form” method=”post”>
and everything works now. Looks like a bug to me?