Hi Fran,
Are you getting that error at the PayPal checkout page or on your own site? I know PayPal has had some issues with their live APIs lately, but as of now their status site shows it’s fixed. Is it still happening to you now? Can you provide a screenshot?
Hi,
Yes it is still happening today. I just tried again.
The error is on the plugin settings page when trying to add a company. So far, I havn’t added any company yet. I’ll just need one company.
Here is what shows after filling all the fields and clicking the button “Add Company”
https://drive.google.com/file/d/0B0h0t_zwll8iZnhhYlZEQmo4QkE/view?usp=sharing
Can you verify what version of PHP, WordPress, and our plugin you are running?
Do you know how to check your PHP error logs on the server to see if that can give us any clues?
That error message is coming from our plugin, and we definitely need to make that more meaningful, but it’s basically happening because the settings were unable to save for some reason. I’ll dig into that a little more, but if you can look for PHP errors that would be helpful.
Hi,
Thanks for keeping on with me.
Checked on my server. PHP version is 7.0
These are the different logs available on my server: web – ftp – error – cgi – out – ssh – cron
I guess the one you mean is “error”. I opened it but I have not enough knowledge to be able to read it properly.
I don’t know if it will help but here it is (error log dated today):
https://pastebin.com/cTuTSd0F
The concerned website: https://fr.hpo-lab.org/
If you need anything else, let me know.
Fran
Well, that’s not the log I was looking for, but it does look like it points out the problem. We’re seeing a bunch of these in there:
WordPress database error Table ‘hpolaborwadbhpo.dbhpo_2_paypal_wp_button_manager_companies’ doesn’t exist for query SELECT count(*) as cnt_company from dbhpo_2_paypal_wp_button_manager_companies made by require_once(‘wp-admin/admin.php’), require_once(‘wp-admin/admin-header.php’), do_action(‘admin_head’), WP_Hook->do_action, WP_Hook->apply_filters, AngellEYE_PayPal_WP_Button_Manager_Admin->paypal_wp_button_manager_print_emptytrash, referer: https://fr.hpo-lab.org/wp-admin/admin.php?page=et_divi_options
So for some reason the database tables that should have been created when you activated the plugin did not get created. Can you try disabling and re-activating the plugin to see if that helps?
Did you set your table prefix for WP in some strange way outside of wp-config, by chance? It’s using this value as the $wpdb->prefix: hpolaborwadbhpo.dbhpo_2_
So I’m actually thinking that the plugin probably did create tables when it was activated, but somehow the tables were created without that prefix. Can you look directly at your db tables to verify what prefix is being used?
Hi,
My table prefix:
I checked in PHPMyAdmin. I see the table prefix is fine for all tables. It’s the prefix I did set in my wp-config.php from the start: dbhpo_
My DB:
In the DB I saw many entries containing “cp_contact_form_paypal” which is one of the paypal plugins I explored. I had removed it though but some plugins don’t clean after themselves…
Anyway, last night I deleted all thoses entries in case they would conflict with your plugin (???). And anyway they had nothing to do there anymore.
I also saw at least one entry concerning your plugin: “dbhpo_3_paypal_wp_button_manager_companies”
My actions:
Last night, not only I disabled your plugin but I removed it. Then I installed it again. When trying again to add a company, I got the same message as before: “Something went wrong”. I just tried again this morning: same thing.
I re-checked my DB in PHPMyAdmin. Here is a screencap of your plugin entry (maybe there are more than one. Not sure:
https://drive.google.com/file/d/0B0h0t_zwll8iY21pVlg5ampDNzQ/view?usp=sharing
Here it is when displayed:
https://drive.google.com/file/d/0B0h0t_zwll8iWk4zd1lvd3NmZEU/view?usp=sharing
I can’t give you better info about this right now because I know nothing about DB. But if you ask me more, I’ll try.
I think I found the kind of error log that you meant.
When looking at it, I see the last found error is dated a few hours before I uninstalled/reinstalled your plugin. But as the plugin still doesn’t work for me anyway, it might not matter. If useful, I can check it again later on and send it to you.
https://pastebin.com/f9WsSyJn
I hope this will help. If needed, I don’t mind giving you any access code you might need in order to see better what’s happening with my system.
Thanks for keeping up with me,
Fran
P.S. I told you your plugin works fine on my own website. On this new website, as a check, I tried to add the same company as on my own website. It didn’t work either. I got “Soemthing went wrong”.
-
This reply was modified 8 years, 8 months ago by
fran330.
Something is going on with your db prefix. You say you have it set to “dbhpo_” but when the code is running it’s using “hpolaborwadbhpo.dbhpo_2_”. Then you also say you’re seeing one as “dbhpo_3_”.
Are you running WordPress multisite, by chance?
I don’t know if this piece of info helps but “hpolaborwadbhpo” is the name of my database and my user name for MySQL.
YES I am running a WP multisite. However my own website (on which your plugin works perfectly) is also a multisite.
Okay, yeah, so I think it’s just adding _2, _3, etc. based on the multisite configuration and somehow those tables aren’t found. Do you see a table in your database at all like “paypal_wp_button_manager_companies”?
Yes, absolutely, it shows in the screen cap I gave you yesterday:
https://drive.google.com/file/d/0B0h0t_zwll8iY21pVlg5ampDNzQ/view?usp=sharing
Here it is when displayed:
https://drive.google.com/file/d/0B0h0t_zwll8iWk4zd1lvd3NmZEU/view?usp=sharing
EDIT (1)
Do you know what? I just added a company on the main site of the network (www.hpo-lab.org). It worked!!!
However I don’t need it there… I need it on the subsite fr.hpo-lab.org and maybe later on my other subsites.
Meanwhile, I’ll check if my DB has other paypal-wp-button tables.
EDIT (2)
No, no other “paypal-wp-button” table.
On my own website (on which your plugin works), I used the plugin on one of the subsites. The DB shows one table “ZA_paypal_wp_button_manager_companies” (ZA being my prefix) AND one other table “ZA_3_paypal_wp_button_manager_companies”. I displayd it and there I saw my 2 company names. So that one concerns that subsite.
-
This reply was modified 8 years, 8 months ago by fran330.
-
This reply was modified 8 years, 8 months ago by fran330.
(Follow up of my previous post)
OK, I found a way out.
As obviously, the plugin works on main site but refuses to deal with subsites, I desactivated it on the network and activated individually on the subsite fr.hpo-lab.org
That made me able to add the company.
To have to activate a plugin individually on each subsite is not the ideal but at least I am happy it works.
If somehow you find an answer to why your plugin doesn”t work on my network, and if it’s fixable, it’ll be great, but it’s not an urgent matter anymore. I needed the paypal button and I now have it.
Thanks a lot for trying to help,
Fran
It’s possible we need to make an adjustment for multi-site use, but I’m surprised this is the first we’re hearing about it. We’ll do some internal testing and include any necessary adjustments in our next update.
Hi,
It might be an exceptional bug somewhere in my install or database, since you never heard about it and also, I can see myself that the problem didn’t occur on my other multisite. So maybe you shouldn’t worry too much about it…
In case the same problem happens to someone else:
1) Desactivate “Paypal WP Button Manager” in network admin
2) Activate it individually on any subsite where you need to use the plugin
3) On each subsite, do what is normally needed in order to add company(ies). If your problem is the same as mine, it should work.
4) Desactivate the plugin on each subsite
5) Activate it again in network admin
7) Now you can add Paypal buttons on any subsite.
At least, this is the way it worked on my install.
Cheers,
Fran
Thanks for the details, Fran. We’ll still look into this and see if we can improve upon the experience.
Sorry for the long delay on this, but we have resolved the issue and it will be fixed in the 1.1.0 update we’ll be releasing very soon.
