PPP Plugin Doesn’t Recognize WooCommerce

  • Resolved shizlist

    (@dnacannon)


    3 years, 1 month ago

    Just installed the Paypal Payments plugin. Already I see an error message in my Woocommerce dashboard that says “WooCommerce PayPal Payments requires WooCommerce to be installed and active. You can download WooCommerce here.” Ironic that I’d be reading a message in woocommerce telling me that I need to install and activate woocommerce.

    Also I don’t see a Paypal option anywhere on the payment settings page. From what I read, this is supposed to appear after activating the PPP plugin.

    SYSTEM REPORT: 

    
### WordPress Environment ###

WordPress address (URL): https://horsedildo.com
Site address (URL): https://horsedildo.com
WC Version: 6.2.0
REST API Version: ? 6.2.0
WC Blocks Version: ? 6.7.3
Action Scheduler Version: ? 3.4.0
WC Admin Version: ? 3.1.0
Log Directory Writable: ?
WP Version: 5.9
WP Multisite: –
WP Memory Limit: 512 MB
WP Debug Mode: ?
WP Cron: ?
Language: en_US
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 7.3.33
PHP Post Max Size: 8 MB
PHP Time Limit: 30
PHP Max Input Vars: 1000
cURL Version: 7.81.0
OpenSSL/1.1.1m

SUHOSIN Installed: –
MySQL Version: 5.7.37
Max Upload Size: 2 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 6.2.0
WC Database Prefix: wpbp_
Total Database Size: 9.99MB
Database Data Size: 7.41MB
Database Index Size: 2.58MB
wpbp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wpbp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wpbp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wpbp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wpbp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_actionscheduler_actions: Data: 0.02MB + Index: 0.11MB + Engine InnoDB
wpbp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_actionscheduler_logs: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_comments: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
wpbp_gla_budget_recommendations: Data: 0.22MB + Index: 0.14MB + Engine InnoDB
wpbp_gla_merchant_issues: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wpbp_gla_shipping_rates: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_gla_shipping_times: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_custom_fields: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_dynamic_segment_filters: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_feature_flags: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_forms: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wpbp_mailpoet_log: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wpbp_mailpoet_mapping_to_external_entities: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_newsletters: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_mailpoet_newsletter_links: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wpbp_mailpoet_newsletter_option: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_newsletter_option_fields: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_newsletter_posts: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_newsletter_segment: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_newsletter_templates: Data: 2.52MB + Index: 0.00MB + Engine InnoDB
wpbp_mailpoet_scheduled_tasks: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_mailpoet_scheduled_task_subscribers: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_segments: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_mailpoet_sending_queues: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_mailpoet_settings: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_statistics_bounces: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wpbp_mailpoet_statistics_clicks: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wpbp_mailpoet_statistics_forms: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_statistics_newsletters: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_mailpoet_statistics_opens: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
wpbp_mailpoet_statistics_unsubscribes: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wpbp_mailpoet_statistics_woocommerce_purchases: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wpbp_mailpoet_stats_notifications: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_mailpoet_subscribers: Data: 0.02MB + Index: 0.13MB + Engine InnoDB
wpbp_mailpoet_subscriber_custom_field: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_subscriber_ips: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_subscriber_segment: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_mailpoet_user_agents: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_mailpoet_user_flags: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_options: Data: 3.06MB + Index: 0.09MB + Engine InnoDB
wpbp_postmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_posts: Data: 0.06MB + Index: 0.06MB + Engine InnoDB
wpbp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_usermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wpbp_wc_admin_notes: Data: 0.05MB + Index: 0.00MB + Engine InnoDB
wpbp_wc_admin_note_actions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wpbp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wpbp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wpbp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wpbp_wc_product_meta_lookup: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
wpbp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wpbp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wpbp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

### Post Type Counts ###

attachment: 1
customize_changeset: 1
mailpoet_page: 1
page: 8
post: 2
revision: 7
wp_global_styles: 1
wpautoterms_page: 4

### Security ###

Secure connection (HTTPS): ?
Hide errors from visitors: ?Error messages should not be shown to visitors.

### Active Plugins (8) ###

WP AutoTerms: by WP AutoTerms – 2.4.9
Google Listings and Ads: by WooCommerce – 1.11.1
Jetpack: by Automattic – 10.6
MailPoet 3 (New): by MailPoet – 3.80.0
WooCommerce Payments: by Automattic – 3.7.0
WooCommerce PayPal Payments: by WooCommerce – 1.6.5
WooCommerce Shipping & Tax: by WooCommerce – 1.25.23
WooCommerce: by Automattic – 6.2.0

### Inactive Plugins (3) ###

Akismet Anti-Spam: by Automattic – 4.2.2
Hello Dolly: by Matt Mullenweg – 1.7.2
Really Simple SSL: by Really Simple Plugins – 5.2.3

### Settings ###

API Enabled: –
Force SSL: –
Currency: USD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
subscription (subscription)
variable (variable)
variable subscription (variable-subscription)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: –

### WC Pages ###

Shop base: #6 - /shop/
Cart: #7 - /cart/
Checkout: #8 - /checkout/
My account: #9 - /my-account/
Terms and conditions: ? Page not set

### Theme ###

Name: Botiga
Version: 1.1.1
Author URL: https://athemes.com
Child Theme: ? – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme
WooCommerce Support: ?

### Templates ###

Overrides: –

### Subscriptions ###

WCS_DEBUG: ? No
Subscriptions Mode: ? Live
Subscriptions Live URL: https://horsedildo.com
Subscription Statuses: –
WooCommerce Account Connected: ? No

### Store Setup ###

Country / State: United States (US) — North Carolina

### Payment Gateway Support ###

WooCommerce Payments: products
refunds
subscriptions
subscription_cancellation
subscription_suspension
subscription_reactivation
subscription_amount_changes
subscription_date_changes
subscription_payment_method_change
subscription_payment_method_change_customer
subscription_payment_method_change_admin
multiple_subscriptions
tokenization
add_payment_method

### WooCommerce Payments ###

Version: 3.7.0
Connected to WPCOM: Yes
Blog ID: 202871155
Account ID: acct_1KTlpT2HaFUZbecu

### Action Scheduler ###

Canceled: 1
Oldest: 2022-02-16 14:06:33 +0000
Newest: 2022-02-16 14:06:33 +0000

Complete: 27
Oldest: 2022-02-14 15:44:44 +0000
Newest: 2022-02-17 12:06:59 +0000

Pending: 2
Oldest: 2022-02-17 13:36:24 +0000
Newest: 2022-02-17 19:13:00 +0000

### Status report information ###

Generated at: 2022-02-17 12:11:57 +00:00
    • This topic was modified 3 years, 1 month ago by shizlist.
    • This topic was modified 3 years, 1 month ago by shizlist.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @dnacannon,

    Something prevents PayPal Payments from properly detecting WooCommerce.
    Could you please give it a try with this version?: https://drive.google.com/uc?export=download&id=1AITvkt6_av-IRZf-65r6hO8yvZ4iFxTj

    There’s an open PR that should help to detect WooCommerce more consistently, for example when set as a MU plugin: https://github.com/woocommerce/woocommerce-paypal-payments/pull/462/commits/eb76bc8f5d27a0a9eb0571477e6791a2939d1659

    The change won’t be included in the upcoming 1.7.0 yet though, so when updating the plugin, you may need to change the code mentioned above manually.
    Anyway, I hope this helps.

    Kind regards,
    Niklas

    Thread Starter shizlist

    (@dnacannon)

    Hi Niklas,

    Thanks. I tried installing that version but got the same result. Error message and no paypal option in the payment settings.

    So the plugin can’t even recognize WooCommerce without adding code? Yikes. Guess that explains the 1.5 star avg rating. Is this plugin really ready for market? Is there another more reliable plugin for processing Paypal payments you’d recommend while all the kinks are getting worked out of this one?

    Also, tried adding the code as shown in the link you sent, it resulted in a critical error when trying to access my dashboard.

    Thanks

    • This reply was modified 3 years, 1 month ago by shizlist.
    • This reply was modified 3 years, 1 month ago by shizlist.
    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @dnacannon,

    Of course, the plugin recognizes WooCommerce. WooCommerce is required to use it in the first place. This integration is used on more than 300.000 sites and works perfectly fine for the vast majority of users.
    But the way it works now, WooCommerce may not be detected properly when installed in a different directory, like the mu-plugins folder.
    PayPal Payments could also fail to detect WooCommerce when changing the WooCommerce folder name and plugin file, which should never be done in the first place. So there are a few edge cases where the detection can be improved, but you seem to misunderstand the problem. There is no need to change the code to detect WooCommerce.
    On your site, in particular, something else prevents the detection from working.

    Can you please check if the behavior persists when you activate the default theme Storefront and disable all plugins and then re-enable WooCommerce and afterward PayPal Payments?
    Thanks!

    Kind regards,
    Niklas

    Thread Starter shizlist

    (@dnacannon)

    Of course, the plugin recognizes WooCommerce.

    Funny, I assumed an error message telling me to install and active woocommerce when it was already installed and activated implied that the plugin didn’t recognize woocommerce. What else could one surmise from this?

    But the way it works now, WooCommerce may not be detected properly when installed in a different directory, like the mu-plugins folder

    There wasn’t any funny business with the installation; for both WooCommerce and the PPP plugin I searched for them via Plugins in WordPress, installed and activated them right there in my dashboard, so I’m not sure how something could have ended up being installed in the wrong directory.

    PayPal Payments could also fail to detect WooCommerce when changing the WooCommerce folder name and plugin file

    Didn’t tinker with the file name at all. So that’s out.

    but you seem to misunderstand the problem. There is no need to change the code to detect WooCommerce.

    Guess I assumed that when you posted a link to a snippet of code and said “there’s an open PR that should help detect woocommerce,” I assumed that meant that you were sending me a code snippet that could help detect woocommerce.

    Can you please check if the behavior persists when you activate the default theme Storefront and disable all plugins and then re-enable WooCommerce and afterward PayPal Payments?

    I’ll give it a whirl.

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @dnacannon,

    A detection issue like this hasn’t come up too often so far, so the error being inaccurate should be an exception to the rule as described with the potential scenarios above. We regret it if it doesn’t work on the first try but that’s why we are here to help.

    What makes me curious is that the WooCommerce readme and license files are not accessible from the default directory on your site.
    So for example, if you add this path to your URL:
    /wp-content/plugins/woocommerce/readme.txt
    Then it will end in a 404.
    This directory from PayPal Payments on the other hand can be accessed:
    /wp-content/plugins/woocommerce-paypal-payments/changelog.txt

    So this makes it seem like either the WooCommerce directory is protected via .htaccess and I’m looking in the wrong direction, or the plugin folder is not actually the default one. It should only be called woocommerce.

    So I would suggest also taking a look at your plugin install directory via FTP to double-check everything is in order there. /wp-content/plugins/woocommerce/
    But if it was just an issue with the folder name, then the test package from my first response should actually resolve the behavior. So it seems more like a plugin conflict, but checking it won’t hurt.
    Thanks!

    Kind regards,
    Niklas

    Thread Starter shizlist

    (@dnacannon)

    Might be onto something there. Here’s a screenshot of my plugins.

    I don’t see woocommerce; I only see woocomerce_bak. Is that the woocommerce plugin? If so, should the file be renamed? Here’s what it contains.

    Also I tried switching to storefront and deactivating all plugins but woocommerce. No dice.

    Thanks

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @dnacannon,

    Thanks for checking, that’s basically what I suspected.
    I don’t know how this came to be when you installed WooCommerce through the official WooCommerce repository, but the woocommerce_bak folder is your regular WooCommerce installation. A _bakfolder extension appears to be the result of a manual or automatic backup but all I can say is this folder should not be named like this.
    For the regular WooCommerce plugin, it doesn’t actually matter what the plugin folder is named as it will work anyway but the name can be relevant for other plugins that attempt to detect WooCommerce.

    I would suggest first creating a full backup of your site + database. Then disable all plugins, and via FTP/cPanel rename the folder woocommerce_bak into woocommerce. Refresh your plugins page, re-enable first WooCommerce and then PayPal Payments to see how it works then. That should do the trick but please let us know if it does not.

    That being said though, scenarios precisely like this should be covered with the package from my first post. The package no longer detects the WooCommerce installation path woocommerce/woocommerce.php but instead the woocommerce class being registered which should make the folder name irrelevant. The PR is fairly straightforward but may need a bit more work as our developers have not yet had the chance to look into it further.

    Kind regards,
    Niklas

    Thread Starter shizlist

    (@dnacannon)

    Voila! Changing the name worked. The error is gone, and Paypal shows up as an option in the settings now. Thanks for the help!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘PPP Plugin Doesn’t Recognize WooCommerce’ is closed to new replies.