Multiple customers of ours are using your plugin. But for some reason today it will let the loginpage crash and also Gravity Forms can’t send any submits when this plugin is enabled.
Can you tell me what is wrong with the plugin and please fix it?
2024/03/28 14:22:47 [error] 716230#716230: *591348 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught TypeError: get_class(): Argument #1 ($object) must be of type object, null given in /home/knipping/knipping.nl/current/wp-content/plugins/download-manager/src/User/Login.php:458
Thanks
Hi,
I use Download Manger Free in site, were logged in users can download files. For login I use standard WP login.
After update 3.2.87 after I logout (I have admin position) I got fatal error.
And then I got “There has been a critical error on this website” all the time.
In server logs I got this message:
Got error ‘PHP message: PHP Fatal error: Uncaught TypeError: get_class(): Argument #1 ($object) must be of type object, null given in /home/……../wp-content/wtyczki/download-manager/src/User/Login.php:359
As you see I use custom name for plugins catalogue, but it’s not the problem.
After deactivating plugin, the site gets back to life.
Is there any chance to cope with this bug?
Thanks in advance.
Marcin
We have started having issues intermittently with PDF Viewer not generating previews and displaying the error: “An error occurred while loading the PDF.” We are running Version 3.0.6. In chatting with our host about seemingly related site speed issues, they confirmed that the WPDM PDF Viewer plugin is throwing out quite a few fatal errors: “NOTICE: PHP message: PHP Fatal error: Uncaught TypeError: method_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in /www/wp-content/plugins/wpdm-pdf-viewer/tpls/viewer.php:68”
They also said: “It also seems like download-manager is throwing out massive amounts of errors as well, over about 8k within the last 2 hours alone so those may be worth having a look at.” We are running Version 6.5.1 of Download Manager Pro.
This site is a core offering to our clients and has behaving very unpredictably. Looking for any quick insight or help you can provide to mitigate these issues please.
Hello,
This error is being thrown on a page where we use a template. It also seems to impact all of our download links throughout the website. When clicking the linked files, for example:
I am redirected to the home page. When clicking on our policies page, where I use a template with a modal pop-up, I get the critical/fatal error:
Kind regards,
-Scott
[08-Jan-2024 19:58:12 UTC] PHP Fatal error: Uncaught Error: Cannot use object of type WP_Error as array in /var/www/neonet.org/wp-content/plugins/wpdm-elementor/src/helper-functions.php:28
Stack trace:
#0 /var/www/neonet.org/wp-content/plugins/wpdm-elementor/src/widgets/CategoryWidget.php(49): get_wpdmcategory_terms()
#1 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/controls-stack.php(2358): WPDM\Elementor\Widgets\CategoryWidget->register_controls()
#2 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/widget-base.php(1044): Elementor\Controls_Stack->init_controls()
#3 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/controls-stack.php(541): Elementor\Widget_Base->init_controls()
#4 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/widget-base.php(181): Elementor\Controls_Stack->get_stack()
#5 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/controls-stack.php(313): Elementor\Widget_Base->get_stack()
#6 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/controls-stack.php(2445): Elementor\Controls_Stack->get_controls()
#7 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/controls-stack.php(1130): Elementor\Controls_Stack->sanitize_settings()
#8 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/controls-stack.php(2190): Elementor\Controls_Stack->get_data()
#9 /var/www/neonet.org/wp-content/plugins/elementor/core/base/base-object.php(142): Elementor\Controls_Stack->get_init_settings()
#10 /var/www/neonet.org/wp-content/plugins/elementor/core/base/base-object.php(40): Elementor\Core\Base\Base_Object->ensure_settings()
#11 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/controls-stack.php(1144): Elementor\Core\Base\Base_Object->get_settings()
#12 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/controls-stack.php(1235): Elementor\Controls_Stack->get_parsed_dynamic_settings()
#13 /var/www/neonet.org/wp-content/plugins/elementskit/modules/wrapper-link/wrapper-link.php(58): Elementor\Controls_Stack->get_settings_for_display()
#14 /var/www/neonet.org/wp-includes/class-wp-hook.php(324): Elementor\ElementsKit_Wrapper_Link->before_section_render()
#15 /var/www/neonet.org/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#16 /var/www/neonet.org/wp-includes/plugin.php(517): WP_Hook->do_action()
#17 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/element-base.php(442): do_action()
#18 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/element-base.php(1375): Elementor\Element_Base->print_element()
#19 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/element-base.php(464): Elementor\Element_Base->print_content()
#20 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/element-base.php(1375): Elementor\Element_Base->print_element()
#21 /var/www/neonet.org/wp-content/plugins/elementor/includes/base/element-base.php(464): Elementor\Element_Base->print_content()
#22 /var/www/neonet.org/wp-content/plugins/elementor/core/base/document.php(1749): Elementor\Element_Base->print_element()
#23 /var/www/neonet.org/wp-content/plugins/elementor/core/base/document.php(1144): Elementor\Core\Base\Document->print_elements()
#24 /var/www/neonet.org/wp-content/plugins/elementor/includes/frontend.php(1179): Elementor\Core\Base\Document->print_elements_with_wrapper()
#25 /var/www/neonet.org/wp-content/plugins/elementor/includes/frontend.php(1074): Elementor\Frontend->get_builder_content()
#26 /var/www/neonet.org/wp-includes/class-wp-hook.php(324): Elementor\Frontend->apply_builder_in_content()
#27 /var/www/neonet.org/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#28 /var/www/neonet.org/wp-includes/post-template.php(256): apply_filters()
#29 /var/www/neonet.org/wp-content/plugins/elementor/modules/page-templates/module.php(190): the_content()
#30 [internal function]: Elementor\Modules\PageTemplates\Module->print_callback()
#31 /var/www/neonet.org/wp-content/plugins/elementor/modules/page-templates/module.php(207): call_user_func()
#32 /var/www/neonet.org/wp-content/plugins/elementor/modules/page-templates/templates/header-footer.php(19): Elementor\Modules\PageTemplates\Module->print_content()
#33 /var/www/neonet.org/wp-includes/template-loader.php(106): include('...')
#34 /var/www/neonet.org/wp-blog-header.php(19): require_once('...')
#35 /var/www/neonet.org/index.php(17): require('...')
#36 {main}
thrown in /var/www/neonet.org/wp-content/plugins/wpdm-elementor/src/helper-functions.php on line 28
These warnings appear inside the log file of the WordPress site, and I do not know what is causing these problems. Use the latest version of your plugins.
[27-Dec-2023 12:46:14 UTC] PHP Warning: Trying to access array offset on value of type null in /home/*********/public_html/wp-content/plugins/download-manager/src/Package/PackageController.php on line 540
[27-Dec-2023 12:46:14 UTC] PHP Fatal error: Uncaught TypeError: method_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in /home/********/public_html/wp-content/plugins/wpdm-pdf-viewer/tpls/viewer.php:68
Stack trace:
#0 /home/******/public_html/wp-content/plugins/wpdm-pdf-viewer/tpls/viewer.php(68): method_exists(NULL, ‘hasPurchased’)
#1 /home/******/public_html/wp-content/plugins/wpdm-pdf-viewer/wpdm-pdf-viewer.php(97): include(‘/home/kutubpdfa…’)
#2 /home/******/public_html/wp-includes/class-wp-hook.php(324): WPDM\AddOn\PDFViwer->viewer(Object(WP))
#3 /home/******/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#4 /home/******/public_html/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
#5 /home/******/public_html/wp-includes/class-wp.php(830): do_action_ref_array(‘wp’, Array)
#6 /home/******/public_html/wp-includes/functions.php(1336): WP->main(”)
#7 /home/******/public_html/wp-blog-header.php(16): wp()
#8 /home/******/public_html/index.php(17): require(‘/home/kutubpdfa…’)
#9 {main}
thrown in /home/******/public_html/wp-content/plugins/wpdm-pdf-viewer/tpls/viewer.php on line 68
[27-Dec-2023 13:41:07 UTC] PHP Warning: Undefined array key 3 in /home/******/public_html/wp-content/themes/******/includes/libs/better-framework/libs/class-bf-color.php on line 61
Is there a solution to these problems or at least an explanation for them?
In WordPress there is a failure with Fatal error: Unparenthesized a ? b : c ? d : e
is not supported. Use either (a ? b : c) ? d : e
or a ? b : (c ? d : e)
in /mnt/web306/e1/40/58821840/htdocs/WordPress_SecureMode_01/wp-content/plugins/download-manager/widgets/class.Search.php on line 17
What can i do?
Hi, I tried to contact you by email, but got no replies
we use version 4.7.7. I can see from WP dash that it is deactivated. And when I try to activate it, I get the following error:
Fatal error: Unparenthesized a ? b : c ? d : e
is not supported. Use either (a ? b : c) ? d : e
or a ? b : (c ? d : e)
in D:\HostingSpaces\PePrime\peprimary.co.uk\wwwroot\wp-content\plugins\download-manager\widgets\class.Search.php on line 17
WordPress reports that it was last updated 2 weeks ago. So the current issues may be related to the recent update
This is in relation to the message I sent you yesterday about the same subject
I have just tried to open our wordpress website (www.peprimary.co.uk) and have had this message coming up:
“Fatal error: Unparenthesized a ? b : c ? d : e
is not supported. Use either (a ? b : c) ? d : e
or a ? b : (c ? d : e)
in D:\HostingSpaces\PePrime\peprimary.co.uk\wwwroot\wp-content\plugins\download-manager\widgets\class.Search.php on line 17
There has been a critical error on your website.
Learn more about debugging in WordPress.”
Any idea why? It seems to have something to do wirth WPDM
Many thanks
We recently purchased the WPDM Pro version to update our very old outdated version of WPDM. Our old version was 4.4.0, which I have been told is a very old Pro version. The old version of our WPDM plugin is so old that the author is “Shaon” not “W3 Eden”. In the old version the WPDM Archive page extension is installed as its own plugin with its own directory under the Plugins directory, and listed as a plugin on the plugins page (Version v2.7.0). When we first update WPDM we get an error when a user tries to access a page with packages on the front end. The “Loading” button just spins in circles indefinitely and we receive the following error in our error log:
PHP Fatal error: Uncaught Error: Class ‘wpdm_pagination’ not found in /nas/content/live/beaconinvstdev/wp-content/plugins/wpdm-archive-page/wpdm-archive-page.php:450#012Stack trace:#012#0 /nas/content/live/beaconinvstdev/wp-includes/class-wp-hook.php(310): WPDM_ArchivePage->GetDownloads(”)#012#1 /nas/content/live/beaconinvstdev/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(NULL, Array)#012#2 /nas/content/live/beaconinvstdev/wp-includes/plugin.php(517): WP_Hook->do_action(Array)#012#3 /nas/content/live/beaconinvstdev/wp-settings.php(654): do_action(‘wp_loaded’)#012#4 /nas/content/live/beaconinvstdev/wp-config.php(127): require_once(‘/nas/content/li…’)#012#5 /nas/content/live/beaconinvstdev/wp-load.php(50): require_once(‘/nas/content/li…’)#012#6 /nas/content/live/beaconinvstdev/wp-blog-header.php(13): require_once(‘/nas/content/li…’)#012#7 /nas/content/live/beaconinvstdev/index.php(17): require(‘/nas/content/li…’)#012#8 {main}#012 thrown in /nas/content/live/beaconinvstdev/wp-content/plugins/wpdm-archive-page/wpdm-archive-page.php on line 450
When we go to the plugins page we see that an update is available for WPDM Archive Page from version v2.7.0 to v4.4.6. When we click to update this we are redirected to the Settings > Updates page where it says “Update” next to WPDM Archive page. One the update button is clicked the Product “WPDM Archive Page” disappears from the list of products and the directory WPDM Archive Page also disappears from the directory itself. WPDM Directory Add – On now says installed (Not sure if this was a replacement for WPDM Archive Page or not). When visiting the front end page the packages are displayed on we now get a new “On Page” error:
[wpdm-archive button_style=”primary” link_template=”560b9d89714c6″ order_by=”post_title” order=”desc” items_per_page=”999″ cat_view=”compact”]
Can someone explain what is going on here and how we can resolve this?
Hello,
I encounter a fatal error on some pages.
Here is the error : Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 5335472600000032 bytes) in /wp-content/plugins/download-manager/src/Package/FileList.php on line 639
I followed these steps from this topic : I’ve updated the plugin to the last version 6.4.1 and clear all cache from Settings > Privacy.
► Nothing changed ! Still got the error
So I followed these steps from this topic : I changed the allowed memory limit in wp-config.php and php.ini files to 2048M (that is quite huge !)
► Nothing changed ! Still got the error
Regarding the recommandation from the error, I should allow at least 5335472600M … which is ludicrous !
What can I do ?
EDIT: while debugging, the variable $fileinfo is empty because in the database table postmeta, the meta_key __wpdm_fileinfo for this post ID does NOT exists
Hello there,
I’ve created a custom small plugin that should interact with your plugin. In one of my file, I sue this code:
namespace package_scanner\model;
use WPDM\Package;
class Post {…}
Now, since some updates on your plugin, I have a fatal error with “use WPDM\Package;”. What’s wrong? What should I change? Do I have to change other things related to this line?
Thank you,
Cedric
I hope this message finds you well. I wanted to inform you that we have successfully downloaded the plugin and uploaded it to our server. However, when we attempted to activate it, we encountered a fatal error that is preventing the plugin from activating.
Fatal error: Uncaught Error: Call to undefined function PrivateMessage\User\wp_date()
in /srv/windowswear.com/subdomains/wwstg/httpdocs/wp-content/plugins/private-message/src/User/User.php on line 34
We kindly request your assistance in resolving this issue at your earliest convenience. If you require any further information or access to our server, please do not hesitate to reach out. Your prompt attention to this matter would be highly appreciated.
Thank you for your support.
Best regards,
Hello,
I’m working on a website that uses Download Manager Pro and revisions are enabled for Download Manager post type.
The fields __wpdm_files, __wpdm_version and __wpdm_fileinfo are included to be saved in revisions.
When I publish or update a Download Manager post type, for example, there is a warning in PHP 7.4 :
Warning: trim() expects parameter 1 to be string, array given in [sitePath]/wp-includes/formatting.php on line 5365
It’s because the normalize_whitespace function expecting a string.
When I use PHP 8.1, it has become a fatal error :
Fatal error: Uncaught TypeError: trim(): Argument #1 ($string) must be of type string, array given in [sitePath]/wp-includes/formatting.php:5365 Stack trace: #0 [sitePath]/wp-includes/formatting.php(5365): trim(Array) #1 [sitePath]/wp-includes/revision.php(163): normalize_whitespace(Array)
How can I include this fields with PHP 8.1 without to patch the normalize_whitespace function ?
Thank you for your help.
David