Search Results for 'fatal error'

Viewing 25 results - 351 through 375 (of 899 total)
  • Author
    Search Results

  • starlink manager
    Participant

    Hello,

    I am trying to evaluate the WPDM Gutenberg Block plugin (3.1.05) as we need to use user registration for downloads but I am receiving the following error and WP ends up in the white screen state:

    “PHP Fatal error: Call to undefined function WPDM\Block\register_block_type() in /var/www/html/wp-content/plugins/wpdm-gutenberg-blocks/libs/blocks/packages.php on line 20”

    Please could any one suggest what the problem might be ?

    Thanks

    Starlink Manager

    #133647

    Luther Davies
    Participant

    I am getting the following error on the Edit User page. The role selection box and save button are missing so modifications to users cannot be made:

    Fatal error: Uncaught Error: Call to undefined function WPDMPP\Libs\wpdm_valueof() in /home/xxx/xxx.com/xxx/wp-content/plugins/wpdm-premium-packages/includes/libs/class.BillingInfo.php:56 Stack trace: #0 /home/xxx/xxx.com/xxx/wp-content/plugins/wpdm-premium-packages/includes/libs/class.BillingInfo.php(72): WPDMPP\Libs\BillingInfo::get(5) #1 /home/xxx/xxx.com/xxx/myredroute/wp-includes/class-wp-hook.php(287): WPDMPP\Libs\BillingInfo->addFields(Object(WP_User)) #2 /home/xxx/xxx.com/xxx/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array) #3 /home/xxx/xxx.com/xxx/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #4 /home/xxx/xxx.com/xxx/wp-admin/user-edit.php(725): do_action(‘edit_user_profi…’, Object(WP_User)) #5 {main} thrown in /home/xxx/xxx.com/xxx/wp-content/plugins/wpdm-premium-packages/includes/libs/class.BillingInfo.php on line 56

    Please advise ASAP!

    Thanks,
    Luther


    Bobby Hayes
    Participant
    This reply has been marked as private.

    Bobby Hayes
    Participant

    No one has bothered to answer any other questions that I have and I still get critical errors when trying to download anything after I updated the membership plugin to version 2.6.5.

    These are the errors I get after updating:

    [15-Jul-2020 13:49:32 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 347
    [15-Jul-2020 13:49:34 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 347
    [15-Jul-2020 13:49:37 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 347
    [15-Jul-2020 13:49:38 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 148267560 bytes) in /wordpress/core/5.4.2/wp-includes/formatting.php on line 2761


    rhalbheer
    Member

    I installed the WPDM Extended Shortdoce package but cannot activate it due:
    Fatal error: Cannot redeclare wpdm_popup_link() (previously declared in /home/www/web284/html/custom/site/wp-content/plugins/download-manager/functions.php:3503) in /home/www/web284/html/custom/site/wp-content/plugins/wpdm-extended-shortcodes/wpdm-extended-shortcodes.php on line 431
    What do I need to change?
    Thank you
    Roger


    Bobby Hayes
    Participant

    These are the errors I’m getting:

    [09-Jul-2020 20:57:27 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:32 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:32 UTC] PHP Notice: Undefined property: stdClass::$title_font_size in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-image-panels/includes/frontend.css.php on line 61
    [09-Jul-2020 20:57:32 UTC] PHP Notice: Undefined property: stdClass::$title_font_size in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-image-panels/includes/frontend.css.php on line 76
    [09-Jul-2020 20:57:34 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:37 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:38 UTC] PHP Warning: Use of undefined constant php – assumed ‘php’ (this will throw an Error in a future version of PHP) in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.css.php on line 252
    [09-Jul-2020 20:57:38 UTC] PHP Warning: Use of undefined constant php – assumed ‘php’ (this will throw an Error in a future version of PHP) in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.css.php on line 254
    [09-Jul-2020 20:57:38 UTC] PHP Warning: Use of undefined constant php – assumed ‘php’ (this will throw an Error in a future version of PHP) in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.css.php on line 284
    [09-Jul-2020 20:57:38 UTC] PHP Deprecated: Non-static method NJBA_Tabs_Module::njbaGetItemContent() should not be called statically in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.php on line 135
    [09-Jul-2020 20:57:38 UTC] PHP Deprecated: Non-static method NJBA_Tabs_Module::njbaGetItemContent() should not be called statically in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.php on line 135
    [09-Jul-2020 20:57:38 UTC] PHP Deprecated: Non-static method NJBA_Tabs_Module::njbaGetItemContent() should not be called statically in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.php on line 135
    [09-Jul-2020 20:57:38 UTC] PHP Deprecated: Non-static method NJBA_Tabs_Module::njbaGetItemContent() should not be called statically in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.php on line 135
    [09-Jul-2020 20:57:38 UTC] PHP Deprecated: Non-static method NJBA_Tabs_Module::njbaGetItemContent() should not be called statically in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.php on line 135
    [09-Jul-2020 20:57:38 UTC] PHP Deprecated: Non-static method NJBA_Tabs_Module::njbaGetItemContent() should not be called statically in /srv/htdocs/wp-content/plugins/ninja-beaver-lite-addons-for-beaver-builder/modules/njba-tabs/includes/frontend.php on line 135
    [09-Jul-2020 20:57:39 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:40 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:42 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:43 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:47 UTC] PHP Warning: Invalid argument supplied for foreach() in /srv/htdocs/wp-content/plugins/wppromembership/functions.php on line 345
    [09-Jul-2020 20:57:47 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 148267560 bytes) in /wordpress/core/5.4.2/wp-includes/formatting.php on line 2761

    #132353

    Krys Petersen
    Participant
    This reply has been marked as private.
    #132137

    Krys Petersen
    Participant
    This reply has been marked as private.
    #131913

    wang ke
    Participant

    Unable to create page template

    The template has been prompted to save successfully, but there is an error message when opening the page template list

    DEBUG INFO:

    Fatal error: Uncaught Error: Class ‘DOMDocument’ not found in /www/wordpress/wp-content/plugins/download-manager/libs/class.PackageTemplate.php:100 Stack trace: #0 /www/wordpress/wp-content/plugins/download-manager/libs/class.PackageTemplate.php(122): WPDM\libs\PackageTemplate->get(‘page-template-c…’, ‘page’) #1 /www/wordpress/wp-content/plugins/download-manager/libs/class.PackageTemplate.php(151): WPDM\libs\PackageTemplate->getCustomTemplates() #2 /www/wordpress/wp-content/plugins/download-manager/admin/tpls/templates/list-templates.php(39): WPDM\libs\PackageTemplate->getTemplates(‘page’) #3 /www/wordpress/wp-content/plugins/download-manager/admin/tpls/templates/templates.php(25): require_once(‘/www/wordpress/…’) #4 /www/wordpress/wp-content/plugins/download-manager/admin/menus/class.Templates.php(82): include(‘/www/wordpress/…’) #5 /www/wordpress/wp-content/plugins/download-manager/admin/menus/class.Templates.php(66): WPDM\admin\menus\Templates::Show() #6 /www/wordpress/wp-includes/class-wp-hook.php(287): WPDM\adm in /www/wordpress/wp-content/plugins/download-manager/libs/class.PackageTemplate.php on line 100


    Syncro Club
    Participant

    When activating I receive a fatal error.

    Parse error: syntax error, unexpected ‘::’ (T_PAAMAYIM_NEKUDOTAYIM) in …/wp-content/plugins/download-manager/libs/class.CategoryHandler.php on line 299

    299 $thtml = WPDM()->package::fetchTemplate($template, $pack);
    solved with
    299 $thtml = WPDM()/Package::fetchTemplate($template, $pack);// WPDM()->package::fetchTemplate($template, $pack)

    Incidentally I discovered I was unable to download the preceding version 3.0.97 totally unavailable !

    Is it mandatory to backup the plugin directory before any update ?

    Sincerely yours

    #131148

    Alex
    Participant

    From one day to another I having the same issue I think.
    Error message on pages with existing categories block:

    Fatal error: Uncaught Error: Call to undefined method WPDM\libs\CategoryHandler::embed() in /var/www/html/alex3d.at/wp-content/plugins/wpdm-gutenberg-blocks/blocks/category.php:96 Stack trace: #0 /var/www/html/alex3d.at/wp-includes/class-wp-block-type.php(109): WPDM\Block\Category->output(Array, ”) #1 /var/www/html/alex3d.at/wp-includes/blocks.php(487): WP_Block_Type->render(Array, ”) #2 /var/www/html/alex3d.at/wp-includes/blocks.php(537): render_block(Array) #3 /var/www/html/alex3d.at/wp-includes/class-wp-hook.php(287): do_blocks(‘<!– wp:paragra…’) #4 /var/www/html/alex3d.at/wp-includes/plugin.php(206): WP_Hook->apply_filters(‘<!– wp:paragra…’, Array) #5 /var/www/html/alex3d.at/wp-includes/post-template.php(253): apply_filters(‘the_content’, ‘<!– wp:paragra…’) #6 /var/www/html/alex3d.at/wp-content/themes/fluida/content/content-page.php(29): the_content() #7 /var/www/html/alex3d.at/wp-includes/template.php(725): require(‘/var/www/html/a…’) #8 /var/www/html/alex3d.at/wp-includes/template.php(672): load_templat in /var/www/html/alex3d.at/wp-content/plugins/wpdm-gutenberg-blocks/blocks/category.php on line 96

    It not even possible to access the backend page using the block editor. Only classic editor works to remove the code.

    Adding a new categories block gives the error “Error loading block: The response is not a valid JSON response.” after choosing a category.

    • This reply was modified 6 years, 3 months ago by Alex.

    Thomas Aurich
    Participant

    Hi there,

    we are using Download Manager Pro with the Gutenberg Blocks Plugin. Right now, the plugin has crashed crippeling the whole page. The error states:

    Fatal error: Uncaught Error: Call to undefined method WPDM\libs\CategoryHandler::embed()
    in /var/www/../../../wp-content/plugins/wpdm-gutenberg-blocks/blocks/category.php on line 96

    Is there a fix?

    Cheers

    Thomas

    #130921

    Ali Khansari
    Participant

    I am the developer, the server is on AWS we didn’t have 500 error in other places but only for this instnace.

    Here is the complete WP error log when you click on the red link (URL) on your Chrome:

    link

    Fatal error: Uncaught Stripe\Error\InvalidRequest: Checkout does not support plans with the value 0 foramountinsubscription_data[items][0]. in /*******/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php:210 from API request ‘req_IvPrCRHaOg61o5’ Stack trace: #0 *******/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php(173): Stripe\ApiRequestor::_specificAPIError(‘{\n “error”: {\n…’, 400, Object(Stripe\Util\CaseInsensitiveArray), Array, Array) #1 /*******/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php(473): Stripe\ApiRequestor->handleErrorResponse(‘{\n “error”: {\n…’, 400, Object(Stripe\Util\CaseInsensitiveArray), Array) #2 /*******/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php(126): Stripe\ApiRequestor->_interpretResponse(‘{\n “error”: {\n…’, 400, Object(Stripe\Uti in /*******/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php on line 210

    When the API is coming back from Stripe servers, it can’t complete the payment process due to the error (there is a parameter that cannot be passed when its value is empty or zero) from Stripe.

    Also, I added another plan that has 1 year interval and it works perfectly fine with Stripe Test mode.

    Can you please take a closer look at your code (where Stripe API is set)? When you choose the lifetime option, maybe it should use a different method (function) not to pass the data for recurring payment method to stripe, but ONE time payment method.

    Does that make sense for you?

    Thanks for your help.

    • This reply was modified 6 years, 3 months ago by Ali Khansari.

    David Hickson
    Participant

    Hi

    I’m trying to upgrade the plugin from Download manager free (Version 3.0.97) to Download manager pro (Version 5.0.95) but keep getting a fatal error message which isn’t allowing me to activate the plugin. This is the message:

    Plugin could not be activated because it triggered a fatal error.
    Parse error: syntax error, unexpected ‘::’ (T_PAAMAYIM_NEKUDOTAYIM) in /public_html/wp-content/plugins/download-manager-new/admin/menus/class.Packages.php on line 142

    Can you please let me know what could be causing the problem?

    Thanks

    #130121

    Peter Havens
    Participant
    This reply has been marked as private.
    #130042

    Scott
    Participant

    Hi Support we are see repeated php errors in our logs as follows which are causing the server to hang, please advise how we fix these as they look to be generated from your plugin?

    [07-Jun-2020 03:21:52 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/customer/www/ingersoll.ca/public_html/wp-content/plugins/download-manager/libs/class.Apply.php on line 832
    [07-Jun-2020 05:21:24 UTC] PHP Warning: Error while sending QUERY packet. PID=55711 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 05:21:24 UTC] PHP Warning: Error while sending QUERY packet. PID=55696 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 05:26:41 UTC] PHP Warning: Error while sending QUERY packet. PID=55862 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 05:26:41 UTC] PHP Warning: Error while sending QUERY packet. PID=55864 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 05:26:41 UTC] PHP Warning: Error while sending QUERY packet. PID=55879 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 05:26:41 UTC] PHP Warning: Error while sending QUERY packet. PID=55887 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 06:11:25 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/customer/www/ingersoll.ca/public_html/wp-content/plugins/download-manager/libs/class.Apply.php on line 832
    [07-Jun-2020 08:15:14 UTC] PHP Warning: array_merge(): Expected parameter 1 to be an array, null given in /home/customer/www/ingersoll.ca/public_html/wp-content/plugins/download-manager/libs/class.Apply.php on line 832
    [07-Jun-2020 11:09:15 UTC] PHP Warning: Error while sending QUERY packet. PID=17838 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 12:17:31 UTC] PHP Warning: Error while sending QUERY packet. PID=21334 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 12:17:31 UTC] PHP Warning: Error while sending QUERY packet. PID=21331 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 12:17:31 UTC] PHP Warning: Error while sending QUERY packet. PID=21322 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 12:17:31 UTC] PHP Warning: Error while sending QUERY packet. PID=21320 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 12:17:31 UTC] PHP Warning: Error while sending QUERY packet. PID=21317 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 12:17:31 UTC] PHP Warning: Error while sending QUERY packet. PID=21329 in /home/customer/www/ingersoll.ca/public_html/wp-includes/wp-db.php on line 2024
    [07-Jun-2020 12:17:53 UTC] PHP Warning: include_once(/home/customer/www/ingersoll.ca/public_html/wp-content/plugins/download-manager/download-manager.php): failed to open stream: No such file or directory in /home/customer/www/ingersoll.ca/public_html/wp-settings.php on line 371
    [07-Jun-2020 12:17:53 UTC] PHP Warning: include_once(): Failed opening ‘/home/customer/www/ingersoll.ca/public_html/wp-content/plugins/download-manager/download-manager.php’ for inclusion (include_path=’.:/usr/local/php73/pear’) in /home/customer/www/ingersoll.ca/public_html/wp-settings.php on line 371
    [07-Jun-2020 12:17:53 UTC] PHP Warning: strpos(): Empty needle in /home/customer/www/ingersoll.ca/public_html/wp-includes/plugin.php on line 687
    [07-Jun-2020 12:17:57 UTC] PHP Warning: strpos(): Empty needle in /home/customer/www/ingersoll.ca/public_html/wp-includes/plugin.php on line 687
    [07-Jun-2020 12:22:55 UTC] PHP Fatal error: Uncaught Error: Class ‘MEC_MEC_widget’ not found in /home/customer/www/ingersoll.ca/public_html/wp-includes/class-wp-widget-factory.php:61
    Stack trace:

    #129704

    Krys Petersen
    Participant

    Hi

    Trying to set up stripe gateway we are getting the following error:

    Please see full error that i am receiving when trying to subscribe using the stripe payment method. We are also on the latest version of the extension/plugins too.

    Fatal error: Uncaught Stripe\Error\InvalidRequest: This value must match the regex pattern. (/\A[a-zA-Z0-9_\-]+\z/ does not match for the value __wppm_mpc member_1591016385). in /nas/content/live/mpcdev2/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php:210 from API request ‘req_1QooF55pxgCKlz’ Stack trace: #0 /nas/content/live/mpcdev2/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php(173): Stripe\ApiRequestor::_specificAPIError(‘{\n “error”: {\n…’, 400, Object(Stripe\Util\CaseInsensitiveArray), Array, Array) #1 /nas/content/live/mpcdev2/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php(473): Stripe\ApiRequestor->handleErrorResponse(‘{\n “error”: {\n…’, 400, Object(Stripe\Util\CaseInsensitiveArray), Array) #2 /nas/content/live/mpcdev2/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php(126): Stripe\ApiRequestor->_interpretResponse(‘{\n “error”: {\n…’, 400, Object(Stripe\Util\CaseIn in /nas/content/live/mpcdev2/wp-content/plugins/wpdmpp-stripe/libs/vendor/stripe/stripe-php/lib/ApiRequestor.php on line 210


    Damiane Muller
    Participant

    Hi guys,

    I have added some roles in the functions.php file using this code

    add_role('student', 'Student', '');

    This created a fatal error on the site. I found this error in the error log:

    [01-Jun-2020 05:48:54 UTC] PHP Fatal error:  Uncaught Error: Cannot unset string offsets in /home/site/dev.siteurl.org.au/wp-includes/class-wp-role.php:75
    Stack trace:
    #0 /home/site/dev.siteurl.org.au/wp-content/plugins/download-manager/libs/class.Apply.php(665): WP_Role->remove_cap('access_server_b...')
    #1 /home/site/dev.siteurl.org.au/wp-includes/class-wp-hook.php(287): WPDM\libs\Apply->sfbAccess('')
    #2 /home/site/dev.siteurl.org.au/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
    #3 /home/site/dev.siteurl.org.au/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #4 /home/site/dev.siteurl.org.au/wp-settings.php(540): do_action('init')
    #5 /home/site/dev.siteurl.org.au/wp-config.php(92): require_once('/home/site/...')
    #6 /home/site/dev.siteurl.org.au/wp-load.php(37): require_once('/home/site/...')
    #7 /home/site/dev.siteurl.org.au/wp-blog-header.php(13): require_once('/home/site/...' in /home/site/dev.siteurl.org.au/wp-includes/class-wp-role.php on line 75

    The fatal error goes away when I disable the Download Manager plugin. Any help would be appreciated.

    #129540

    Shahjada
    Keymaster

    @@helrefaie, extremely sorry for your inconvenience. The issue was around the stats entry, and triggering a fatal error. However, I’ve have adjusted the issue, and download is working fine now. We also added the patch on our side so that you can continue with the upcoming updates smoothly. Thanks for your patience.

    #129254

    D Patrick
    Participant

    I’m needing assistance ASAP.
    I’m getting this error while trying to activate the Download Manager Pro plugin! https://prnt.sc/souvm2

    It says Plugin could not be activated because it triggered a fatal error.
    Parse error: syntax error, unexpected ‘::’ (T_PAAMAYIM_NEKUDOTAYIM) in /chroot/home/a6751794/marketing.sswhitedental.com/html/wp-content/plugins/download-manager/admin/menus/class.Packages.php on line 142


    Breni Malpass
    Participant

    Help! Purchased Pro version but cannot activate. Uploaded successfully. When I try to activate I get this error…

    Plugin could not be activated because it triggered a fatal error.

    Parse error: syntax error, unexpected ‘::’ (T_PAAMAYIM_NEKUDOTAYIM) in /home4/seasidm0/public_html/wp-content/plugins/download-manager/admin/menus/class.Packages.php on line 142

    #128945

    In reply to: Purchased and upgraded


    Michael
    Participant
    This reply has been marked as private.
    #128938

    Michael
    Participant

    Users were having problems adding downloads, were getting an error. Couldn’t find a solution so purchased upgrade to hopefully fix the error.

    Instead it has made things worse. When a user goes to upload they enter the title, but there’s no submit button after they enter the title. You have to hit the return key to bring the next part up.

    Once that’s been brought up, it switches into what looks like mobile view (the whole area is squeezed into the middle of the screen) it then reports a fatal error if you add a file.

    Please can you fix this as soon as possible, I’m expecting a lot of new downloads via my users.

    I will provide logins if needed in private.

    https://prnt.sc/smd4gu

    https://prnt.sc/smd5m8

    • This topic was modified 6 years, 4 months ago by Michael. Reason: added screenshots
    #128119

    In reply to: Yoast Compatability


    Simon Harvey
    Participant
    This reply has been marked as private.

    B
    Participant

    Hi,

    We did not get any fatal errors when installing, and we cannot see any indications now that the installation was unsuccessful. We did exactly what you described in a previous post, so the procedure should be correct as well.

    I am starting to suspect that you might be logging into the original creator of this thread’s website, and not ours. We had a similar issue, so I posted in this thread, but our credentials are posted further down in the thread history.

    I have 3 questions, could you please address them all?

    1. Are you sure that you are logging in to the correct website?
    2. Should I create a new thread on this issue such that we are the creators of the thread?
    3. Could you please tell me were you get your information on WPDM, WPDM API status? We have never seen the same information/status as you, so we really want to know were you get yours

Viewing 25 results - 351 through 375 (of 899 total)