White page after 1.3.79 – 1.3.80
-
After the update to version 1.3.79, only the homepage is displayed. The other pages are completely blank with an error code of 500. I came back in 1.3.78 and it works again. Site in production for several months without change. What is happening ?
https://depadoc.be
-
On my local server with the same site copy I have:
(!) Fatal error: Uncaught Error: Call to a member function get_element_trid () is null in F: \ wamp64 \ www \ siberia.dlinkddns.com \ depadoc \ wp-content \ plugins \ ultimate-member \ core \ um-logout .php on line 38
(!) Error: Call to a member function get_element_trid () is null in F: \ wamp64 \ www \ siberia.dlinkddns.com \ depadoc \ wp-content \ plugins \ ultimate-member \ core \ um-logout.php on line 38
Call Stack
# Time Memory Function Location
1 0.0003 385896 {main} () … \ index.php: 0
2 387968 0.0005 require ( ‘F: \ wamp64 \ www \ myserver \ depadoc \ wp-blog-header.php’) … \ index.php: 17
3 54,125,624 1.1720 require_once ( ‘F: \ wamp64 \ www \ myserver \ depadoc \ wp-includes \ template-loader.php’) … \ wp-blog-header.php: 19
4 1.1720 54,125,672 do_action () … \ template-loader.php: 12
5 1.1720 54126080 WP_Hook-> do_action () … \ plugin.php: 453
6 1.1721 54126112 WP_Hook-> apply_filters () … \ class-wp-hook.php: 323
7 1.1921 54539648 UM_Logout-> logout_page () … \ class-wp-hook.php: 298If that can help you (update from 1.3.78 to 1.3.80)
When I remove this line (38)
$ Trid = $ sitepress-> get_element_trid ($ current_page_ID);
in ultimate-member/core/um-logout.php, everything looks to work.
Hi,
Can you please try the pre-release version 1.3.81 in the link?
https://github.com/ultimatemember/ultimatemember/releasesIt has fixes to this issue. Let us know if this resolves the issue on your end.
Regards,
I just try it’s the same problem but on line 40
( ! ) Fatal error: Uncaught Error: Call to a member function get_element_trid() on null in F:\wamp64\www\siberia.dlinkddns.com\depadoc\wp-content\plugins\ultimate-member\core\um-logout.php on line 40
( ! ) Error: Call to a member function get_element_trid() on null in F:\wamp64\www\siberia.dlinkddns.com\depadoc\wp-content\plugins\ultimate-member\core\um-logout.php on line 40
Call Stack
# Time Memory Function Location
1 0.0003 385896 {main}( ) …\index.php:0
2 0.0005 387968 require( ‘F:\wamp64\www\siberia.dlinkddns.com\depadoc\wp-blog-header.php’ ) …\index.php:17
3 1.1828 54117384 require_once( ‘F:\wamp64\www\siberia.dlinkddns.com\depadoc\wp-includes\template-loader.php’ ) …\wp-blog-header.php:19
4 1.1828 54117432 do_action( ) …\template-loader.php:12
5 1.1828 54117840 WP_Hook->do_action( ) …\plugin.php:453
6 1.1828 54117872 WP_Hook->apply_filters( ) …\class-wp-hook.php:323
7 1.2032 54531408 UM_Logout->logout_page( ) …\class-wp-hook.php:298I do not understand too much because on another site in development with your plug-in I do not have the problem! (HERE no concern https://cgsp.bulgaweb.com). I had had a weird message about the logout on this one.
By cons on the first (depadoc.be) it has been online for a while and I only made one update. The pages remain blank except the homepage, even when trying to view a page from the wordpress back-end.
The difference must come in my opinion from the fact that I have Polylang on this site (depadoc) after seeing Fix WPML compatibility with UM logout!
On the site of my client I removed the line $ trid = $ sitepress-> get_element_trid ($ current_page_ID);
And the site looks to work without it. I do not know if it’s important?Bruno
- This reply was modified 7 years, 10 months ago by pirardbruno.
Hi,
Thanks for letting us know. It looks like a plugin conflict with PolyLang.
I’m working on this issue now.
I’ll get back to you.
Regards,
Hi @pirardbruno,
Can you please the pre-release version 1.3.82 in the link?
https://github.com/ultimatemember/ultimatemember/releasesLet me know if this resolves the issue.
Regards,
It’s always the same thing.
Fatal error: Uncaught Error: Call to a member function get_element_trid() on null in F:\wamp64\www\siberia.dlinkddns.com\depadoc\wp-content\plugins\ultimate-member\core\um-logout.php on line 40
( ! ) Error: Call to a member function get_element_trid() on null in F:\wamp64\www\siberia.dlinkddns.com\depadoc\wp-content\plugins\ultimate-member\core\um-logout.php on line 40
Call Stack
# Time Memory Function Location
1 0.0004 385896 {main}( ) …\index.php:0
2 0.0006 387968 require( ‘F:\wamp64\www\siberia.dlinkddns.com\depadoc\wp-blog-header.php’ ) …\index.php:17
3 1.1787 54117880 require_once( ‘F:\wamp64\www\siberia.dlinkddns.com\depadoc\wp-includes\template-loader.php’ ) …\wp-blog-header.php:19
4 1.1787 54117928 do_action( ) …\template-loader.php:12
5 1.1787 54118336 WP_Hook->do_action( ) …\plugin.php:453
6 1.1787 54118368 WP_Hook->apply_filters( ) …\class-wp-hook.php:323
7 1.1991 54531904 UM_Logout->logout_page( ) …\class-wp-hook.php:298And if I delete line 40 no more worries …
Bruno
Hello,
I have exactly the same problem :
Fatal error: Call to a member function get_element_trid() on null in /wp-content/plugins/ultimate-member/core/um-logout.php on line 40
The version I use is 1.3.81.
Thanks for your help,
- This reply was modified 7 years, 10 months ago by vladimir-slonska.
Hi Vladimir, they are working on the problem. Attention also because I had the worry, Ultimate Member does not work with PHP 7.1. Actually you can upgrade to 1.3.81 and then you can go to change in the plugin utlimate-member / core / um-logout.php.
It is necessary to remove (make a backup before) the line “
$ Trid = $ sitepress-> get_element_trid ($ current_page_ID);” (Currently line 40, 38 in the previous version 1.3.79).Normally at home just by clearing this line everything works correctly.
I have two site with Ultimate Member, the second in development does not have Polylang and there I have no problem. It is with Polylang that there is a conflict.
I hope it will help you
Bruno
- This reply was modified 7 years, 10 months ago by pirardbruno.
- This reply was modified 7 years, 10 months ago by pirardbruno.
- This reply was modified 7 years, 10 months ago by pirardbruno.
Bonjour,
Merci beaucoup de la réponse. J’attends aussi donc le résultat.
I also have another very big problem. I have a default record that uses “multi-select” fields. On the registration page everything goes well as you can see here https://cgsp.bulgaweb.com/saffilier-en-ligne/
When I go into editing the profile, if I take “Or do you work?” I have only 2 raws! And normally my forms have + – 10.
Privacy – Everyone
Visibility – Everywhere
Can edit this field – yes
I make a mistake or it’s a bug?Bruno
For the last post, it’s my mistake. The two forms are separate and independent and the second was not updated as the first.
SorryThe pre-released version 1.3.82 is working fine for me.
Thank you for warning me. I just tried and there’s no problem with Polylang.
I have also this bug in /um-logout.php on line 40 …and website could not work like this… hope there is a solution…
- The topic ‘White page after 1.3.79 – 1.3.80’ is closed to new replies.