Pay Now feature having a conflict with Database

Home › Forums › WC Vendors Pro Support › Pay Now feature having a conflict with Database

NOTICE: We've Moved to a Ticket System for Support

As of August 31, 2017 (12am EST) our support forums will be retired (read-only), and we will be moving to a support ticket system.  This will allow us to better organize and answer support requests, and provide a more personalized experience as we assist our customers.

For the time being, we will leave our forums open for reading and learning while we work on creating a more robust Knowledge Base for everyone to use.

If you are a WC Vendors Pro customer please open a support ticket here. 

If you are a WC Vendors user please open a support ticket on the Wordpress.org forums.

The information on this forum is outdated and in most instances no longer relevant. Please be sure to check our documentation for the most up to date information.

https://docs.wcvendors.com/

Thank you to all of our customers!

 

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • July 14, 2016 at 8:33 pm #37241
    Douglas
    Participant

    Hello WC Vendors,

    I am having a rare problem, I tried all the solutions in similar cases and as suggested, before submitting I’ve spent countless hours searching for a solution with no results. Sorry to take your time but I am desperate at this point.

    Here’s what happens, when choosing pay “now” for vendor payment, the result is an Error 500. After reading something very similar here I tried everything with no results. In desperation, I reinstalled everything, including WordPress. This is when I noticed that perhaps the database is the problem. At first the new installs had the same error but then I installed the same theme and plugins in the same server under the same domain but with a new database. This time the pay “now” worked fine. When I updated the wp-config file to return to the former database, the problem returned. I already have several vendors and products in the original database so I need to use it.

    Do you have any suggestions? possible fix?

    The nice guys that made the theme are trying to help but this is the first time they face this problem.

    Any advise will be enormously appreciated!

    Thank you in advance!

    July 14, 2016 at 8:55 pm #37242
    Douglas
    Participant

    Skip to main contentSkip to toolbar

    Dashboard
    Home
    Updates

    Posts
    All Posts
    Add New
    Categories
    Tags

    Media
    Library
    Add New

    Pages
    All Pages
    Add New

    Comments

    Contact
    Contact Forms
    Add New
    Integration

    Suppamenu Pro

    PageBuilder

    Email Subscribers
    Subscribers
    Compose
    Notification
    Send Email
    Cron Mail
    Settings
    Roles
    Sent Mails
    Help & Info

    WooCommerce
    Orders
    Coupons
    WC Vendors
    Commission
    Reports
    Settings
    System Status
    Add-ons

    Products
    Products
    Add Product
    Categories
    Tags
    Attributes

    Envato Toolkit

    Appearance
    Themes
    Customize
    Widgets
    Menus
    Header
    Background
    Handy Theme Options
    Editor

    YITH Plugins
    Compare
    Wishlist
    Ajax Product Filter
    How to install premium version

    Plugins
    Installed Plugins
    Add New
    Editor

    Users
    All Users
    Add New
    Your Profile
    Import From CSV

    Tools
    Available Tools
    Import
    Export
    Rebuild Thumbnails
    Widget Settings Import
    Widget Settings Export

    Settings
    General
    Writing
    Reading
    Discussion
    Media
    Permalinks
    Twiget Settings
    Coming Soon Page & Maintenance Mode

    Google Maps Easy
    Overview
    Add Map
    All Maps
    Maps Import / Export
    Marker Categories
    Settings

    Slider Revolution
    Slider Revolution
    Navigation Editor
    Add-Ons
    Collapse menu
    About WordPress
    Hemptsy
    00 comments awaiting moderation
    New
    Howdy, phearnandoavatar
    Maintenance Mode Active
    Log Out
    Help
    System StatusToolsLogsSystem Status
    Please copy and paste this information in your ticket when contacting support:
    Get System Report Understanding the Status Report
    WordPress Environment
    Home URL: http://hemptsy.com
    Site URL: http://hemptsy.com
    WC Version: 2.6.2
    Log Directory Writable: /home6/hemptsyc/public_html/wp-content/uploads/wc-logs/
    WP Version: 4.5.3
    WP Multisite: –
    WP Memory Limit: 256 MB
    WP Debug Mode: –
    WP Cron:
    Language: en_US
    Server Environment
    Server Info: Apache
    PHP Version: 5.6.17
    PHP Post Max Size: 64 MB
    PHP Time Limit: 30
    PHP Max Input Vars: 1000
    cURL Version: 7.24.0, OpenSSL/1.0.0
    SUHOSIN Installed: –
    Max Upload Size: 64 MB
    Default Timezone is UTC:
    fsockopen/cURL:
    SoapClient:
    DOMDocument:
    GZip:
    Multibyte String:
    Remote Post:
    Remote Get:
    Database
    WC Database Version: 2.6.2
    woocommerce_sessions
    woocommerce_api_keys
    woocommerce_attribute_taxonomies
    woocommerce_downloadable_product_permissions
    woocommerce_order_items
    woocommerce_order_itemmeta
    woocommerce_tax_rates
    woocommerce_tax_rate_locations
    woocommerce_shipping_zones
    woocommerce_shipping_zone_locations
    woocommerce_shipping_zone_methods
    woocommerce_payment_tokens
    woocommerce_payment_tokenmeta
    Active Plugins (17)
    AJAX Thumbnail Rebuild by junkcoder – 1.12
    Coming Soon Page & Maintenance Mode by SeedProd by SeedProd – 5.0.3
    Contact Form 7 by Takayuki Miyoshi – 4.4.2
    PageBuilder for Handy Store by – 1.0
    Email Subscribers by Store Apps – 3.1.4
    Envato WordPress Toolkit by Envato – 1.7.3
    Google Maps Easy by supsystic.com – 1.5.9
    Import Users from CSV by Ulrich Sossou – 1.0.0
    Slider Revolution by ThemePunch – 5.2.4.1
    .Suppamenu Pro by Sabri Taieb – 2.6.2
    Twiget Twitter Widget CUST by Prasanna SP -C – 1.1.4
    WC Vendors by WC Vendors – 1.9.1
    Widget Data – Setting Import/Export Plugin by Voce Communications – Kevin Langley, Sean McCafferty, Mark Parolisi – 1.5.0
    WooCommerce by WooThemes – 2.6.2
    YITH WooCommerce Ajax Product Filter by YITHEMES – 3.0.4
    YITH WooCommerce Compare by YITHEMES – 2.0.9
    YITH WooCommerce Wishlist by YITHEMES – 2.0.16
    Settings
    Force SSL: –
    Currency USD ($)
    Currency Position left
    Thousand Separator ,
    Decimal Separator .
    Number of Decimals 2
    API
    API Enabled:
    WC Pages
    Shop Base: #4 – /shop/
    Cart: #5 – /cart/
    Checkout: #6 – /checkout/
    My Account: #7 – /my-account/
    Taxonomies
    Product Types: external (external), grouped (grouped), simple (simple), variable (variable)
    Theme
    Name: HandyStore Child
    Version: 4.1 (see readme.txt for detailed changelog)
    Author URL: http://themes.zone
    Child Theme:
    Parent Theme Name: HandyStore
    Parent Theme Version: 4.7 (see readme.txt for detailed changelog)
    Parent Theme Author URL: https://themes.zone
    WooCommerce Support:
    Templates
    Overrides (WooCommerce): handystore/woocommerce/archive-product.php,
    handystore/woocommerce/cart/cart.php,
    handystore/woocommerce/checkout/review-order.php,
    handystore/woocommerce/content-product.php,
    handystore/woocommerce/content-widget-product.php,
    handystore/woocommerce/loop/add-to-cart.php,
    handystore/woocommerce/loop/loop-start.php,
    handystore/woocommerce/single-product/product-image.php,
    handystore/woocommerce/single-product/rating.php
    If you like WooCommerce please leave us a ★★★★★ rating. A huge thank you from WooThemes in advance! Version 4.5.3

    July 18, 2016 at 1:34 pm #37454
    Douglas
    Participant

    Hello again! Any chance you have a suggestion to solve my problem?

    July 18, 2016 at 1:57 pm #37455
    WC Vendors Support
    Participant

    Hi Douglas!

    Error 500 means “Internal Server Error”. While it isnt terribly descriptive, that’s OK, it wasnt meant to be. Those types of errors are logged in your webservers error_log file. Your webhosting company can tell you how to find it, it’s just a big text file. Make the error happen, then open the error_log and look at the last few errors in it and let me know what they say!

    Ben

    July 19, 2016 at 2:41 pm #37609
    WC Vendors Support
    Participant

    [19-Jul-2016 02:49:48 UTC] PHP Fatal error: Cannot redeclare class OAuthException in /home6/hemptsyc/public_html/wp-content/plugins/wc-vendors/classes/gateways/PayPal_Masspay/api/lib/auth/PPAuth.php on line 0

    Boom. There’s the issue. Let’s debug it section by section:

    PHP Fatal error – This means your website will crash when this error occurs, as opposed to a warning or a notice which you can generally ignore.

    Cannot redeclare class OAuthException in........ — This tells you that another plugin is trying to load PayPal’s Mass Pay API at the same time WC Vendors is. This means you have two plugins installed and activated that are doing the same thing and conflicting with each other.

    This is why, before submitting a post, you’re instructed to disable all other plugins, and test. Had you done that, you would have seen this is a plugin conflict, and that the resolution is to use only one paypalap plugin, the one that comes with WC Vendors. 🙂

    Have fun

    July 21, 2016 at 7:26 pm #37846
    Douglas
    Participant

    Ben, if for some reason you cannot find what is causing the error, could you suggest on how to transfer all users, vendors and their products to a new database? We are eager to get our website running again.

    Thanks again!!

    July 22, 2016 at 2:21 pm #37930
    WC Vendors Support
    Participant

    None of those errors are WC Vendors related. I’m sorry, you’re on your own for those. We can only support/fix things WC Vendors related……..

    July 22, 2016 at 3:37 pm #37952
    Douglas
    Participant

    wait! please don’t abandon us yet! We love your product and want to continue using it!

    Is this not related?

    [20-Jul-2016 15:45:17 UTC] PHP Fatal error: Cannot redeclare class OAuthException in /home6/hemptsyc/public_html/wp-content/plugins/wc-vendors/classes/gateways/PayPal_Masspay/api/lib/auth/PPAuth.php on line 0

    July 25, 2016 at 2:19 pm #38144
    WC Vendors Support
    Participant

    Paste me 300 lines of errors, I’m gonna skim them. 😉

    The PHP fatal error you see there is related to WC Vendors, and is a problem. That error means you have TWO PayPal adaptive payments plugins installed and activated. Why? Disable the other one. WC Vendors includes the only one you can use, the other wont even work. 🙂

    July 25, 2016 at 6:42 pm #38167
    Douglas
    Participant

    Hey Ben, thanks for getting back and sorry for the 300 lines of errors, it’s just that we are desperate at this point since our site can’t pay vendors.

    Just wanted to make clear that the only plugins we have installed are WC Vendors, WC Vendors pro and WooCommerce, only those 3.

    Where else could this extra paypal code be? We de-activated WC Vendors but Pro requieres it to work correct?

    Seriously, thanks for your time

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • The forum ‘WC Vendors Pro Support’ is closed to new topics and replies.