Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

βœ… πŸ”— 🐞 Bug Report: Fatal Error after updating to 3.7.7 (Duplicate of #19894) #19917

Closed
5 tasks done
ciprianpentelescu opened this issue Sep 26, 2022 · 2 comments
Labels
bug Indicates a bug with one or multiple components. compatibility/3rd-party Indicates a compatibility problem with a 3rd-party plugin or theme. mod* solved Indicates that an Issue has been Solved, or a Feature Request has been Released. status/merged Indicates when a Pull Request has been merged to a Release. type/developer-api Indicates when a topic is related to the Developer API and Documentation. type/responsive Indicates when a topic is related to Responsive Design, for tablet, mobile, and other screens.

Comments

@ciprianpentelescu
Copy link

ciprianpentelescu commented Sep 26, 2022

Prerequisites

  • I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
  • The issue still exists against the latest stable version of Elementor.

Description

After updating today the site stops working, and i get this fatal error:

PHP Fatal error: Uncaught TypeError: Elementor\Core\Files\CSS\Base::get_style_control_value(): Argument #1 ($control) must be of type array, null given, called in /public_html/wp-content/plugins/elementor/core/files/css/base.php on line 682 and defined in /public_html/wp-content/plugins/elementor/core/files/css/base.php:738Stack trace:#0 /public_html/wp-content/plugins/elementor/core/files/css/base.php(682): Elementor\Core\Files\CSS\Base->get_style_control_value()#1 [internal function]: Elementor\Core\Files\CSS\Base->Elementor\Core\Files\CSS\{closure}()#2 /public_html/wp-content/plugins/elementor/core/files/css/base.php(448): call_user_func()#3 /public_html/wp-content/plugins/elementor/core/files/css/base.php(347): Elementor\Core\Files\CSS\Base->parse_property_placeholder()#4 [internal function]: Elementor\Core\Files\CSS\Base->Elementor\Core\Files\CSS\{closure}()#5 /public_html/wp-content/plugins/elementor...',

Steps to reproduce

Updated from 3.7.7 to 3.7.6. In console there is a swiper error and the website is down.
Also i have JetPopup 1.5.6 installed

Isolating the problem

  • This bug happens with only Elementor plugin active (and Elementor Pro).
  • This bug happens with a Blank WordPress theme active (Hello theme).
  • I can reproduce this bug consistently using the steps above.

System Info

Centos 7, PHP 8.1

@ciprianpentelescu ciprianpentelescu added the status/awaiting_triage Indicates when an Issue, Pull Request, or Discussion awaits to be triaged. label Sep 26, 2022
@DanielRuf
Copy link

Duplicate of #19894 which was unfortunately closed.

As a workaround see #19894 (comment)

@nicholaszein nicholaszein added bug Indicates a bug with one or multiple components. compatibility/3rd-party Indicates a compatibility problem with a 3rd-party plugin or theme. type/responsive Indicates when a topic is related to Responsive Design, for tablet, mobile, and other screens. type/developer-api Indicates when a topic is related to the Developer API and Documentation. and removed status/awaiting_triage Indicates when an Issue, Pull Request, or Discussion awaits to be triaged. labels Sep 28, 2022
@nicholaszein
Copy link
Contributor

nicholaszein commented Sep 28, 2022

Hello @ciprianpentelescu!

Thank you for contacting us.

You seem to have a conflict with a 3rd party add-on that is using an unsupported method, not included in our API.

We are already aware of this issue, and a fix will be released in the upcoming patch version. Meanwhile, please Rollback Elementor to version 3.7.6.
You can use the built-in rollback feature or simply download this file and upload it as a plugin to your website. It will ask you if you want to replace Elementor v3.7.7 with v3.7.6. Just click to replace it and everything should be back to normal.

πŸ“‹ This issue is a Duplicate of #19894, which is on the same subject. For this reason, I'm closing this issue and ↔️ Merging it with the original, so we can have all the discussion in one location, and deal with it more efficiently.

Please feel free to continue the conversation there. πŸ˜‰

Best regards,

Nick

@nicholaszein nicholaszein closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2022
@nicholaszein nicholaszein changed the title Fatal Error after updating to 3.7.7 🐞 Bug Report: Fatal Error after updating to 3.7.7 (Duplicate of #19894) Sep 28, 2022
TzviRabinovitch pushed a commit that referenced this issue Oct 19, 2022
… [ED-8329] (#19883)

## PR Type
What kind of change does this PR introduce?
<!-- Please check the one that applies to this PR using "x" with no
spaces eg: [x]. -->
- [X] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] CI related changes
- [ ] Documentation content changes
- [ ] Other... Please describe:

## Summary

This PR can be summarized in the following changelog entry:

* Fix: Custom background position not inherited on mobile and front end
(Fixes: #19924)
* Fix: Responsive controls with responsive conditions whose values are
arrays (Base Multiple) did not apply in the front end for non-desktop
devices.
* Fix: In certain edge cases, third party addons crash pages since
v3.7.7 (Fixes: #19917, #19922 as well as problems raised in the comments
of #19894)

## Description
An explanation of what is done in this PR

* If a responsive control was conditioned upon another responsive
control, and that conditioning control was a Base Multiple control
(which means - the control value was an array(PHP)/object(JS) - such as
Slider controls [size, unit]) - the responsive values were not applied
in the front end
@nicholaszein nicholaszein changed the title 🐞 Bug Report: Fatal Error after updating to 3.7.7 (Duplicate of #19894) πŸ”— 🐞 Bug Report: Fatal Error after updating to 3.7.7 (Duplicate of #19894) Oct 19, 2022
@nicholaszein nicholaszein changed the title πŸ”— 🐞 Bug Report: Fatal Error after updating to 3.7.7 (Duplicate of #19894) βœ… πŸ”— 🐞 Bug Report: Fatal Error after updating to 3.7.7 (Duplicate of #19894) May 24, 2023
@elementor elementor locked and limited conversation to collaborators May 24, 2023
@nicholaszein nicholaszein added status/merged Indicates when a Pull Request has been merged to a Release. solved Indicates that an Issue has been Solved, or a Feature Request has been Released. labels May 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Indicates a bug with one or multiple components. compatibility/3rd-party Indicates a compatibility problem with a 3rd-party plugin or theme. mod* solved Indicates that an Issue has been Solved, or a Feature Request has been Released. status/merged Indicates when a Pull Request has been merged to a Release. type/developer-api Indicates when a topic is related to the Developer API and Documentation. type/responsive Indicates when a topic is related to Responsive Design, for tablet, mobile, and other screens.
Projects
None yet
Development

No branches or pull requests

3 participants