diff --git a/.browserslistrc b/.browserslistrc
index a7d888b50797..c076e797c5e7 100644
--- a/.browserslistrc
+++ b/.browserslistrc
@@ -1,2 +1,9 @@
last 3 versions
+Chrome >= 100
+Firefox >= 100
+Edge >= 100
+Safari >= 15.5
+iOS >= 15.5
+Android >= 100
+ChromeAndroid >= 100
not dead
diff --git a/.cursor/rules/general-code-style.mdc b/.cursor/rules/general-code-style.mdc
new file mode 100644
index 000000000000..fdec4c4ac79d
--- /dev/null
+++ b/.cursor/rules/general-code-style.mdc
@@ -0,0 +1,21 @@
+---
+description:
+globs:
+alwaysApply: true
+---
+# Code Style
+
+## Avoid Magic Numbers
+- Do not use unexplained hardcoded values ("magic numbers") in code or tests.
+- Define such values as named constants or use existing constants to clarify their meaning.
+
+## Consistent Error Codes and Status
+- When returning error codes and HTTP status, always be very specific to use the correct code, not only 200 and 500.
+
+## Prioritize Style and Developer Experience
+- Always pay attention for clarity, maintainability, and ease of understanding, even if the underlying logic does not change.
+- Code style and developer experience are important for long-term project health.
+
+## Self Documented Code
+- Avoid adding comments that can be a constants or a well named function
+- Always prefer to create small funcitons that describe themself
diff --git a/.cursor/rules/tests-code-style.mdc b/.cursor/rules/tests-code-style.mdc
new file mode 100644
index 000000000000..c96cf9556864
--- /dev/null
+++ b/.cursor/rules/tests-code-style.mdc
@@ -0,0 +1,10 @@
+---
+description:
+globs: *test*
+alwaysApply: false
+---
+# Testing Best Practices
+
+## Reduce Code Duplication
+- For repeated code such as test setup, mocks or assertions, extract them into helper methods or setup functions.
+- Example: If multiple tests initialize the same mocks or objects, move this logic to a shared setup function rather than duplicating code in each test.
diff --git a/.env.example b/.env.example
index 90075cd7ac8f..b7036b34b956 100644
--- a/.env.example
+++ b/.env.example
@@ -1,4 +1,4 @@
USERNAME=admin
PASSWORD=password
BASE_URL=http://localhost:8888
-ELEMENTS_REGRESSION_BASE_URL=http://localhost:8888
+ELEMENTS_REGRESSION_BASE_URL=http://localhost:8889
diff --git a/.eslintignore b/.eslintignore
index 208b7a688edc..66bd1358b887 100644
--- a/.eslintignore
+++ b/.eslintignore
@@ -3,7 +3,10 @@ assets/js/
**/*.min.js
**/node_modules/**
**/vendor/**
+**/vendor_prefixed/**
build/**
-packages/**/*
tests/qunit/setup/tinymce.js
/tmp/**
+packages/**/*
+eslint-local-rules.js
+.eslintrc.js
diff --git a/.eslintrc.js b/.eslintrc.js
index 6338a53caaee..4c5ab67bdaae 100644
--- a/.eslintrc.js
+++ b/.eslintrc.js
@@ -3,15 +3,14 @@ module.exports = {
'plugin:react/recommended',
'plugin:no-jquery/deprecated',
'plugin:@wordpress/eslint-plugin/recommended-with-formatting',
- 'plugin:@elementor/editor/recommended',
'plugin:import/typescript',
],
plugins: [
'babel',
'react',
- '@elementor/editor',
'no-jquery',
'@typescript-eslint',
+ 'local-rules',
],
parser: '@typescript-eslint/parser',
globals: {
@@ -53,11 +52,19 @@ module.exports = {
'@typescript-eslint/await-thenable': 'error',
'@typescript-eslint/no-var-requires': 'error',
'@typescript-eslint/ban-ts-comment': 'error',
+ // Local rules
+ 'local-rules:no-react-namespace': 'error',
},
parserOptions: {
project: [ './tsconfig.json' ],
},
},
+ {
+ files: [ 'tests/**/*.ts', 'tests/**/*.tsx' ],
+ rules: {
+ 'local-rules:no-react-namespace': 'off',
+ },
+ },
],
rules: {
// Custom canceled rules
diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md
index 43e451004664..44736bce4129 100644
--- a/.github/CODE_OF_CONDUCT.md
+++ b/.github/CODE_OF_CONDUCT.md
@@ -2,73 +2,104 @@

-**The Elementor GitHub organization page and all respective repositories are collaborative spaces for web creators, developers, enthusiasts, and users alike to contribute, share ideas, and help shape the future of Elementor in a positive and welcoming way.**
+**The Elementor GitHub organization and its repositories are collaborative spaces for web creators, developers, enthusiasts, and users to contribute, share ideas, and help shape the future of Elementor in a positive and welcoming way.**
-All participants are expected to follow this Code of Conduct without exceptions.
+All participants are expected to follow this Code of Conduct — without exception.
+
+
## Our Pledge
-In the interest of fostering an open, inclusive, and welcoming environment, we strive to maintain, in all collaborative spaces, an undiscriminatory and harassment-free experience for everyone, regardless of skill level, ability, disability, socioeconomic status, political inclination, age, appearance, nationality, ethnicity, gender identity, sexual orientation, or religion.
+To foster an open, inclusive, and respectful environment, we are committed to providing a harassment-free and equitable experience for everyone — regardless of skill level, ability, socioeconomic status, political belief, age, appearance, nationality, ethnicity, gender identity, sexual orientation, or religion.
-This Code of Conduct outlines our expectations for all those who participate in any Elementor GitHub space, as well as the consequences of unacceptable behavior.
+This Code of Conduct outlines expectations for everyone participating in any Elementor GitHub space, as well as the consequences of violating these expectations.
-**We invite all those who participate to help us create safe and positive experiences for everyone.**
+**We invite all contributors to help us make this a welcoming and positive experience for everyone.**
+
+
## Guidelines
-To ensure everyone has a good, welcoming, and positive experience, we outlined a few rules that should be followed and enforced by all participants.
+To ensure that everyone feels welcome and safe, we ask all participants to follow these guidelines:
-### Be Respectful and Empathetic
+### Be Respecful and Kind
-We embrace healthy conversations but don't tolerate behavior that disrespects or discriminates against other contributors or maintainers. Be aware of diverse backgrounds and perspectives.
-
-**Let's make this a safe space for anyone to contribute and share ideas.**
+Treat everyone with kindness and consideration. We welcome healthy discussions, but we do not tolerate disrespect, discrimination, or exclusionary behavior.
### Be Welcoming and Open-minded
-Our spaces are open for contributors with any experience level. Be receptive to other ideas or points of view and welcoming to all contributors, especially those who are inexperienced.
+Our community is open to contributors of all backgrounds and experience levels. Be patient, especially with newcomers. Value different perspectives.
+
+### Be constructive and stay on topic
+
+Critique ideas, not individuals.
+Keep discussions relevant to Elementor products — political, religious, or unrelated topics are not allowed.
-### Be Constructive, Relevant and keep the conversation On-topic
+> _Inflammatory, offensive, or off-topic discussions may be removed without warning or explanation._
-Criticize ideas, not people.
- Explain your thoughts and keep discussions relevant to Elementor products. We don't engage in talks about politics, religion, or other unrelated topics.
+### Stay organized
-**Heated, offensive, and off-topic discussions will be removed at our discretion without warning or requiring any explanation.**
+Help maintain a clean and navigable community by following these best practices:
-### Keep it tidy
+- Follow our [Contribution Guidelines](https://elemn.to/gh-contributing).
+- Use [Issues](https://elemn.to/gh-issues) only for reproducible bugs.
+- Use [Feature Request discussions](https://elemn.to/gh-feature-requests) to request new features.
+- Do not use GitHub for support requests or complaints — use our [official support channels](https://elemn.to/support-ticket).
+- Search before opening new threads.
+- Troubleshoot before reporting bugs.
+- Stay on topic in all conversations.
+- Do not use unrelated issues to post new bugs or feature requests.
+- Avoid “+1” or “Agreed” comments — use the upvote button where available.
+- Provide complete information when asked, especially when triaging or debugging.
+
+
-Organize and submit your issues, discussions, and comments correctly:
+## Expected Behavior
-- **Always follow** our [Contribution Guidelines](https://elemn.to/gh-contributing).
-- Submit [Issues](https://elemn.to/gh-issues) **only to report bugs.**
-- Submit [Feature Request Discussions](https://elemn.to/gh-feature-requests) **only to request features.**
-- Don't use any space to request support or to file complaints. **Use the official Elementor support channels** instead.
-- **Search before submitting** new threads to avoid duplicates.
-- **Troubleshoot** your issues before submitting a bug report.
-- **Provide instant and thorough information** when requested.
-- **Stay on topic** when commenting.
-- **Don't use other issues or discussions to report different bugs or feature requests.** Instead, submit new ones or join the ones that are already open.
-- Avoid commenting _"+1"_ or _"Agreed,"_ **use the upvote button** when available.
+We expect participants to:
-## Expected behaviors
+- Be respectful and inclusive
+- Assume good intent
+- Listen actively and respond constructively
+- Acknowledge mistakes and learn from them
+- Create a welcoming atmosphere for everyone
+
+
-We're here to create a positive and welcoming environment.
- Always be respectful, show empathy, respect differing opinions, give and accept feedback gracefully, apologize for mistakes, and focus on keeping all spaces welcoming for all contributors by following our Guidelines above.
+## Unacceptable Behavior
-## Unacceptable behaviors
+We do not tolerate:
-Please avoid inappropriate behavior, including using offensive or sexualized language, trolling, harassment, discrimination, disclosing private information without permission, spam or off-topic discussions, and posting complaints about the Elementor company or other subjects.
+- Harassment, trolling, or personal attacks
+- Discrimination or exclusionary comments
+- Sexualized or inappropriate language or content
+- Disclosing private or personal information without consent
+- Spam, off-topic content, or disruptive behavior
+- Using GitHub to submit complaints about the company or staff
+
+
## Enforcement
-Our maintainers will enforce these guidelines and take fair action if necessary.
+Moderators and maintainers are responsible for upholding this Code of Conduct and may take appropriate action, including:
+
+- Removing content
+- Locking or closing threads
+- Issuing warnings or temporary bans
+- Enforcing permanent bans in cases of repeated or severe violations
+
+These actions may be taken without warning or explanation, at the discretion of the moderation team.
-We reserve the right to close, lock, or remove any thread or comment at any time without warning or explanation. Continuing inappropriate behavior will result in a permanent ban at our discretion.
+This Code of Conduct applies across all Elementor GitHub spaces — including Issues, Discussions, Pull Requests, and Comments.
+
+
-**This Code of Conduct applies to all Elementor GitHub pages and spaces, including but not limited to Issues and Discussions.**
+## Reporting Concerns
-If you wish to file a complaint, please [reach out to Elementor Support](https://elemn.to/contact).
+If you experience or witness behavior that violates this Code of Conduct, please [contact Elementor Support](https://elemn.to/contact). We will review all reports and take them seriously.
+
+
## Attribution
-Our Code of Conduct is an adaptation of the [Contributor Covenant](https://www.contributor-covenant.org/) and the [GitHub Community Code of Conduct](https://docs.github.com/en/site-policy/github-terms/github-community-code-of-conduct).
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/) and the [GitHub Community Code of Conduct](https://docs.github.com/en/site-policy/github-terms/github-community-code-of-conduct).
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index bac7595342e5..785d37344edf 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -7,32 +7,54 @@
Community contributions are always welcomed and help us remain the Number 1 WordPress Website Builder. Contributors can answer questions on all Elementor GitHub spaces or submit their contributions in the appropriate channels.
**Before submitting contributions, all participants should read and follow these Guidelines and our [Code of Conduct](https://elemn.to/gh-code-of-conduct).**
+
+
## How to use GitHub
We use GitHub **exclusively** for well-documented **Bug Reports**, **Feature Requests** and **Code Contributions (Pull Requests)**.
Communication should always be in **English**.
-### Need Help, Guidance, Assistance, or Support?
+For any other topic, please use the appropriate channels. For all things Elementor visit our website: [https://elementor.com](https://elementor.com/?utm_source=github-repo&utm_medium=link&utm_campaign=contribution).
+
+
-**Note that we are unable to offer any support through this repository.**
+> [!NOTE]
+> ### Contributing to Editor V4
+>
+> We are currently collecting feedback and reports for the new **Editor V4**, a complete re-architecture of the Elementor Editor focused on performance, modularity, and a CSS-first design system.
+>
+> If you're testing **Editor V4**, please use the following dedicated forms:
+>
+> - [Report bugs in Editor V4](https://elemn.to/editor-v4-issues)
+> - [Join discussions and share feedback](https://elemn.to/editor-v4-feedback)
+>
+> Please note that the **Editor V4** is in active development, may be unstable, and may lack some functionality found in Elementor V3. Use it only in testing environments, and make sure to review the scope and purpose of each form before submitting your reports or feedback.
+
-Please **DO NOT** open issues or discussions to request support.
+### Need Personal Help, Guidance, Assistance, or Support?
+
+**Note that we are unable to offer any level of support through this repository.**
+
+Please **DO NOT** open issues or discussions to request for Personal Support.
For those, use the appropriate channels.
**Find out how to [submit a Support Ticket here](https://elemn.to/support-ticket).**
Alternatively, you can visit one of these resources:
-- **Help Center** Visit the [Elementor Help Center](https://elemn.to/gh-to-help-center) to find solutions to the most frequent problems, or read the documentation about Elementor's many features.
-- **Academy** Grow your Web Creator skills and learn to make the most of Elementor in the [Elementor Academy](https://elemn.to/gh-to-academy).
+- **Help Center** Visit the [Elementor Help Center](https://elemn.to/help) to find solutions to the most frequent problems, or read the documentation about Elementor's many features.
+- **Academy** Grow your Web Creator skills and learn to make the most of Elementor in the [Elementor Academy](https://elemn.to/academy).
+- **Discord Community** Connect and chat with other Web Creator in different channels (including on multiple languages) through our official [Elementor Discord Community](https://elemn.to/discord).
- **Global Community** Join the [Elementor Global Community](https://elemn.to/community-on-fb) on Facebook. Where all kinds of users come together to help each other.
- **Support Forum** If you have more questions, visit the free [Support Forum](https://elemn.to/wp-support-forum) on our WordPress plugin page.
-- **Elementor Website** For more information about features, FAQs, and documentation, check out our website at [Elementor Website Builder](https://elemn.to/gh-to-elementor).
+- **Elementor Website** For more information about features, FAQs, and documentation, check out our website at [Elementor Website Builder](https://elementor.com/?utm_source=github-repo&utm_medium=link&utm_campaign=contribution).
-**If you have an active [Elementor Pro](https://elemn.to/gh-to-elementor-pro) subscription, you are entitled to personal support. Please see your purchase email or visit your [Elementor Account page](https://elemn.to/my-elementor) for details.**
+**If you have an active [Elementor Pro](https://elemn.to/gh-to-elementor-pro) subscription, you are entitled to personal support. Please see your purchase email or visit your [Elementor Account page](https://my.elementor.com) for details.**
**As a gentle reminder, we may close support requests submitted to GitHub spaces without action.**
+
+
## How to report Security Issues
@@ -45,45 +67,154 @@ We leverage the collective expertise of our community, offering round-the-clock
Join our [Managed Security Bug Bounty programs](https://elemn.to/gh-to-bounty-programs) instead and help us maintain Elementor, a secure software, responsibly.
**To learn more about our security efforts and how to contact us for security inquiries, please visit our [Trust Center](https://elemn.to/gh-to-trust-center).**
+
+
## How to Report a Bug
If you found a bug in the source code and can reproduce it consistently after troubleshooting it, you can help us by [submitting a Bug Report](https://elemn.to/gh-new-bug-report).
-### Before submitting your Bug Report, follow these best practices to help save time
+### Requirements
+
+To help us review and resolve your report efficiently, all submitted bug reports must meet the following requirements. These rules ensure that reported issues are actionable, reproducible, and relevant.
+
+- **All fields in the bug report form are required — no exceptions.**
+ Missing or incomplete information leads to unnecessary delays and often makes issues unreviewable. Issues missing required fields may be closed without review.
+
+- **Search for similar issues before opening a new one.**
+ Duplicate reports create unnecessary noise and slow down the triaging process. Before posting, search the [open and closed issues](https://elemn.to/gh-issues) to see if your problem has already been reported or addressed.
+
+- **Ensure you are using the latest stable versions.**
+ Bugs that occur in outdated versions may already be fixed. Please make sure Elementor, Elementor Pro, WordPress core, your theme, and all plugins are up to date.
+ Check the [changelog](https://elemn.to/changelog).
+
+- **Clear all levels of cache.**
+ Issues caused by outdated or conflicting cached data are common. Before submitting a report, clear your browser cache, CDN cache, plugin cache, and server cache — in that order — to avoid false positives.
+
+- **Test with only Elementor, Elementor Pro, and the Hello Elementor theme active.**
+ Conflicts from third-party plugins or themes are not actionable by our team. Isolate the issue by deactivating all unrelated plugins and switching to the Hello theme before reporting the problem.
+ See: [Troubleshooting the Editor](https://elemn.to/help-troubleshooting)
+
+- **Include your full Elementor System Info.**
+ This diagnostic report helps us understand your environment and replicate the issue. Reports submitted without this information will be closed.
+ [How to get your System Info](https://elemn.to/help-system-info)
+
+- **If you are a third-party developer, please identify yourself.**
+ Include your name, company, and a way to reach you. If your report involves compatibility with your own plugin, theme, or integration, this helps us follow up appropriately.
+
+- **Only one issue per report.**
+ Submitting multiple bugs in a single issue makes tracking and resolving them harder. Please open separate reports for separate problems.
+
+### Scope
+
+We can only accept bug reports that fall within the scope of what we actively support. Submissions that do not meet this criteria will be closed without action.
+
+- **Requests for personal support**
+ GitHub is not an efficient support channel. For assistance with setup, common issues, troubleshooting, or how-to questions, please contact our [Support Team](https://elemn.to/support-ticket) or visit our [Help Center](https://elemn.to/help).
+
+- **Conflicts with third-party plugins, themes, or services**
+ If the issue only occurs when using tools not officially supported by Elementor, please contact the third-party developer. We do not triage or resolve external compatibility issues.
+
+- **Feature requests or missing functionality**
+ If something is not broken but simply not yet supported, it's not a bug. Please use the [Feature Request form](https://elemn.to/gh-new-feature-request) instead.
+
+- **Custom code and unsupported modifications**
+ We cannot help debug issues related to custom snippets, hooks, filters, overrides, or undocumented modifications. Refer to our [Developer Documentation](https://elemn.to/dev-docs) if you're building custom integrations.
+
+- **Security issues**
+ We take security very seriously. And we want to resolved in a responsible manner. Please, do not disclose vulnerabilities as bug reports. Use our [Bug Bounty Program](https://elemn.to/gh-to-bounty-programs) for coordinated and responsible security reporting.
+
+- **Complaints, or inappropriate content**
+ GitHub issues are not the right place for complaints about Elementor's products, services, or policies. Reach out to Elementor Support Instead. We also do not tolerate hostile, discriminatory, or disrespectful remarks. See our [Code of Conduct](https://elemn.to/gh-code-of-conduct).
+
+- **Invalid, incomplete, or vague reports**
+ Reports missing required fields, lacking reproduction steps, or submitted without proper validation will be closed to maintain the quality and focus of the issue tracker.
+
+### Instructions
+
+To ensure we can understand and resolve the issue effectively, follow these writing guidelines when filling out the form:
-- **Search Before Posting** Please [search for similar issues](https://elemn.to/gh-issues) (both open and closed) to prevent creating duplicates. Use [GitHub Labels](https://elemn.to/gh-labels) to refine your search.
-- **Stay Up-to-date** Ensure you are using the [most recent and stable versions](https://elemn.to/changelog) of Elementor (and Elementor Pro), as well as all installed plugins, themes, and WordPress.
-- **Troubleshoot your Issue** Visit our [Help Center](https://elemn.to/gh-to-help-center) and use the search function to find [troubleshooting articles](https://elemn.to/help-troubleshooting) for the most common problems that can be solved quickly.
-- **Isolate the Problem and Validate your Issue** Ensure your issue happens when only the **Elementor (and Elementor Pro)** plugins are active while also using the [Hello Elementor theme](https://elemn.to/wp-hello-elementor-theme). Isolating the problem helps identify if Elementor causes the issue you're experiencing
-- **Write a Clear and Concise Title** Summarize your title in a short sentence that can help identify your issue at a glance without needing to read the description.
-- **Provide a Detailed Description** Please help us understand in detail what problems you are experiencing. Give a detailed description of your problem, and provide examples, screenshots, screen recordings, and related links.
-- **Explain how we can Recreate your Issue** Enumerate all the steps needed to reproduce the issue in detail so we can replicate it in our environment.
-- **Tell us what you were Expecting to Happen** Describe the **Expected Behavior** to help identify the root of the issue.
-- **Share the Elementor System Info** Be ready to share a full copy of the [Elementor System Info](https://elemn.to/help-system-info) report from your WordPress **`Dashboard`** > **`Elementor`** > **`System Info`** page (available at the bottom of the page). **We won't accept issues without it. [Learn how to copy it here](https://elemn.to/help-system-info).**
-- **Write One Bug Report per Issue** If you are experiencing more than one bug, submit only **ONE BUG PER ISSUE**.
+- **Use a clear and descriptive title**
+ A well-written title helps other users (and our team) quickly understand what the report is about and whether it might be related to other reports.
-**As a gentle reminder, we may close issues that do not comply with these guidelines without action.**
+- **Describe the issue in detail**
+ Explain what happened, when it happened, and what part of Elementor is affected. Include any error messages, behavior patterns, and relevant context. Screenshots and screen recordings are especially helpful.
+
+- **List all steps to reproduce the issue**
+ Reproduction steps are essential for verifying and fixing bugs. Provide a step-by-step guide of what you did, so we can reproduce it - ideally on a clean WordPress install. If we cannot reproduce the issue, we cannot resolve it.
+
+- **Explain what you expected to happen**
+ Make clear what the correct or intended behavior should be. This helps us understand if the issue is due to a bug, a misunderstanding, or a missing feature.
+
+**As a gentle reminder, issues that do not meet these guidelines may be closed without further action. These standards ensure that our team and community contributors can manage reports effectively and focus on actionable feedback.**
+
+
## How to Request a Feature
-Do you have a brilliant idea, enhancement, or feature you would love to see in Elementor? We're all ears!
+Have an idea to improve Elementor? We're always open to feedback that helps us create better tools for web creators. If you'd like to request a new feature or enhancement, you can do so by [submitting a Feature Request](https://elemn.to/gh-new-feature-request).
+
+You can also support existing ideas by [voting for your favorite requests](https://elemn.to/gh-feature-requests).
+
+
+### Requirements
+
+To help us evaluate suggestions effectively, all submitted feature requests must meet the following requirements. These rules ensure each request is unique, well-defined, and relevant to Elementor's core product vision.
+
+- **Search for existing requests before posting.**
+ Duplicate requests reduce clarity and fragment community support. Please search both [open and closed requests](https://elemn.to/gh-feature-requests) to avoid duplicates. Prefer to always Vote for existing requests instead of submitting new ones.
+
+- **Verify that the feature is not already available.**
+ Before suggesting a new feature, check the [Features page](https://elemn.to/features) and your current Elementor setup to confirm it doesn't already exist.
+
+- **Submit only one request per thread.**
+ Submitting multiple suggestions in one request makes it harder to discuss, prioritize, and track individual ideas. Use one form per idea.
+
+- **Be specific about what problem the feature solves.**
+ A request that's grounded in a clear problem is easier to evaluate and more likely to be prioritized. Vague requests or "nice-to-have" ideas without a real use case may be closed.
+
+- **Explain your proposed solution clearly.**
+ The more detail you provide, the easier it is for our team (and the community) to understand how this could be implemented ad Vote for it.
+
+### Scope
+
+To stay focused and productive, we may close requests that do not meet the following criteria:
+
+- **Out of scope for Elementor's core mission.**
+ Requests that require major architectural changes, niche workflows, or overlap with third-party integrations that Elementor doesn't directly support may fall outside the product roadmap.
+
+- **Already supported or recently released features.**
+ If the feature already exists or was just released, we may close the request and link to the existing implementation.
+
+- **Bug reports, support requests, or custom code questions.**
+ These belong in other dedicated forms. Please report confirmed bugs using the [Bug Report form](https://elemn.to/gh-new-bug-report), and use [Support Channels](https://elemn.to/support-ticket) for troubleshooting or help with custom code.
+
+- **Low-detail or unclear submissions.**
+ Requests lacking context, justification, or clear value may be closed to keep the list relevant and actionable.
+
+### Instructions
+
+To ensure your suggestion is well understood, please include the following in your request:
+
+- **A clear and descriptive title.**
+ Helps others quickly understand the purpose of your request.
+
+- **The problem it solves.**
+ Describe the need or limitation this feature would address.
-Suggest new ideas, features, or enhancements by [submitting a Feature Request](https://elemn.to/gh-new-feature-request).
- You can also support existing ideas by [voting for your favorite requests](https://elemn.to/gh-feature-requests).
+- **Your proposed solution.**
+ Explain what you'd like to see added or changed in Elementor.
-### Before submitting a new Feature Request, follow these best practices to help save time
+- **Any alternatives you've considered.**
+ If you've tried workarounds or plugins, share your experience.
-- **Search Before Posting** Before creating a new Feature Request, please [search for similar requests](https://elemn.to/gh-feature-requests) to prevent creating duplicates.
-- **Confirm Before Posting** Please check the [Elementor Features page](https://elemn.to/features) before posting to avoid requesting an existing feature.
-- **Write a Clear and Concise Title** Summarize your title in a short sentence that can help identify your request at a glance without needing to read the description.
-- **Provide a Detailed Description** Elaborate on how you envision the feature. Include examples, use cases, and any other relevant details.
-- **Describe the Solution** Describe how you'd like a solution to be implemented.
-- **Provide Alternatives** Mention any alternative solutions or workarounds you've considered.
-- **Give Additional Context** Add context to your suggestion by providing examples, screenshots, screen recordings, related links, and additional information that might help us understand your request better.
-- **Write One Request Per Thread** If you have multiple requests, please submit only **ONE REQUEST PER THREAD**.
+- **Extra context.**
+ Screenshots, examples, or links to related ideas can help others understand your vision.
+
-**As a gentle reminder, we may close requests that do not comply with these guidelines without action.**
+**As a gentle reminder, Feature Request discussions that do not meet these guidelines may be closed without further action. These standards ensure that our team and community contributors can manage reports effectively and focus on actionable feedback.**
+
+
## I want to Contribute
@@ -128,5 +259,5 @@ Your contributions, big or small, play a significant part in the continued devel
- [Elementor Developers Center](https://elemn.to/gh-to-dev-center)
- [Elementor Developers Documentation](https://elemn.to/gh-to-dev-docs)
-- [GitHub Support and General Documentation](https://elemn.to/gh-support-center)
-- [GitHub Pull Request Documentation](https://elemn.to/gh-support-pull-requests)
+- [GitHub's official Support and General Documentation](https://elemn.to/gh-support-center)
+- [GitHub's official Pull Request Documentation](https://elemn.to/gh-support-pull-requests)
diff --git a/.github/DISCUSSION_TEMPLATE/editor-v4.yml b/.github/DISCUSSION_TEMPLATE/editor-v4.yml
new file mode 100644
index 000000000000..9fb42f6aa197
--- /dev/null
+++ b/.github/DISCUSSION_TEMPLATE/editor-v4.yml
@@ -0,0 +1,59 @@
+labels: ["product/editor-v4"]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ # 🧪 Editor V4 Discussion Form
+
+
+ 👋 **Welcome, and thank you for helping shape the future of Elementor!**
+
+ We're thrilled to have you here testing **Editor V4** - a major evolution of the Elementor Editor, rebuilt to improve performance, responsiveness, and your overall workflow.
+
+ **This space is for sharing your thoughts, insights, and suggestions about Editor V4's features. Your feedback is incredibly valuable and helps guide the direction of the product during its development.**
+
+ Want to learn more about Editor V4? **[Visit our Editor V4 landing page](https://elemn.to/editor-v4)**, it will be updated regularly!
+
+
+ ## 🧭 Guidelines
+
+ Before getting started, please take a moment to review our **[Contribution Guidelines](https://elemn.to/gh-contributing)** and **[Code of Conduct](https://elemn.to/gh-code-of-conduct)**. These help us keep this space organized, respectful, and inclusive for everyone.
+
+
+ > [!IMPORTANT]
+ > ### 🧪 This space is dedicated to discussing the Editor V4, its features, and progress.
+ >
+ > If you're here to report a bug in the **Editor V4**, please use the **[🐛 Editor V4 Bug Report form](https://elemn.to/editor-v4-new-issue)** instead.
+ >
+ > ℹ️ Keep in mind **the Editor V4 is still a work in progress** - it may not include all existing features from Elementor V3, is subject to change or instability, and should not be used on production websites.
+ >
+ > ⚠️ _**Discussions that are unrelated to the Editor V4 may be closed without further action.**_ _**Be kind. Keep this space positive, respectful, and welcoming.**_
+
+
+ ## 💡 Help Us Keep Editor V4 Discussions Organized
+
+ - 🔍 **[Search for existing Editor V4 discussions](https://elemn.to/editor-v4-feedback)**. Someone may have already started a thread on the same topic. Add your thoughts there to keep conversations centralized.
+
+ - ✒️ **Use a clear and descriptive title.** A good title helps others quickly understand what your post is about, and participate on the discussion instead of creating a new one.
+
+ - ☝️ **Stick to one topic per discussion thread.** This makes it easier to track feedback and follow up on specific subjects.
+ - type: textarea
+ id: description
+ validations:
+ required: true
+ attributes:
+ label: "Description"
+ description: "Please share your thoughts, feedback, or questions about the Editor V4 below."
+ placeholder: "Start a discussion about the Editor V4..."
+ - type: markdown
+ attributes:
+ value: |
+
+ - type: checkboxes
+ id: final_agreement
+ attributes:
+ label: "Agreement"
+ description: "By filling out this form, you confirm that you have read the guidelines outlined above, and you agree your discussion may be closed without warning if it doesn't meet them."
+ options:
+ - label: "I confirm I have read and followed the Editor V4 Discussion Form guidelines, and agree this discussion may be closed without warning."
+ required: true
diff --git a/.github/DISCUSSION_TEMPLATE/feature-request.yml b/.github/DISCUSSION_TEMPLATE/feature-request.yml
index 49309ee1b90d..f3ec37cd820a 100644
--- a/.github/DISCUSSION_TEMPLATE/feature-request.yml
+++ b/.github/DISCUSSION_TEMPLATE/feature-request.yml
@@ -3,102 +3,115 @@ body:
- type: markdown
attributes:
value: |
- **👋 Hello, welcome to Elementor Feature Requests!**
- # ⚠️ BEFORE POSTING READ THIS CAREFULLY
- ## 🚀 Please only use this form to request an Elementor feature or enhancement.
- **🚩 Check our [Roadmap](https://elemn.to/gh-to-roadmap) to learn what's in the pipeline.**
- ### 🛟 Need Help, Guidance, Assistance, or Support? [Click here to get support](https://elemn.to/support-ticket).
- ### 🐞 Need to Report an Elementor Bug? [Click here to report a bug](https://elemn.to/gh-new-bug-report).
-
- **ℹ️ For more information, please read our [Contribution Guidelines](https://elemn.to/gh-contributing).**
+ # 🚀 Request a Feature or Enhancement in Elementor
- ### 😉 Follow these best practices to help save time
- - ✒️ **Write a Clear and Concise Title** Summarize your title in a short sentence that can help identify your request at a glance without needing to read the description.
- - ☝️ **One Request Per Thread** If you have multiple requests, please submit only **ONE REQUEST PER THREAD**. Requests with more than one subject may be closed without action.
-
+ 👋 **Hello, and thank you for helping shape the future of Elementor!**
+ Use this form to suggest new features or enhancements that could improve Elementor.
- ### ✳️ Fill-in all required fields!
- - ❌ Requests lacking detail or submitted for any other reason than to suggest new ideas, features, or enhancements for the Elementor plugin may be closed without action.
-
+ ## 🧭 Guidelines
- ---
+ Before getting started, please take a moment to review our **[Contribution Guidelines](https://elemn.to/gh-contributing)** and **[Code of Conduct](https://elemn.to/gh-code-of-conduct)**. These help us keep this space organized, respectful, and inclusive for everyone.
- ## THE REQUEST
- ### 📋 Prerequisites
- - 🔍 **Search Before Posting** Before creating a new Feature Request, please [search for similar requests](https://elemn.to/gh-feature-requests) to prevent creating duplicates.
- - ✔️ **Confirm Before Posting** Please check the [Elementor Features page](https://elemn.to/features) before posting to avoid requesting an existing feature.
- - type: checkboxes
- id: prerequisites
- attributes:
- label: "Prerequisites"
- options:
- - label: "I have searched for similar feature requests in both open and closed discussions and cannot find an existing request."
- required: true
- - label: "I have verified that the feature is still missing from the latest stable versions of Elementor or Elementor Pro."
- required: true
- - type: markdown
- attributes:
- value: |
-
+ > [!IMPORTANT]
+ > ### 🚀 This form is specifically for requesting features or enhancements in Elementor.
+ > If you're experiencing a confirmed bug, and can reproduce it consistently after troubleshooting it, please use the **[🐞 Bug Report Form](https://elemn.to/gh-new-bug-report)** instead.
+ >
+ > For Personal Help, Assistance or Support, please use one of our **[🛟 Personal Support Channels](https://elemn.to/support-ticket)** instead.
+ >
+ > Before posting, make sure the feature doesn't already exist by checking the **[✔️ Features Page](https://elemn.to/features)** and our **[🚩 Roadmap](https://elemn.to/roadmap)**.
+ >
+ > ⚠️ _**Submitting unrelated or incomplete discussions may result in them being closed without further action.**_
+
+
+
+
📋 Requirements
(click to expand)
+
+ To increase the chances of your request being selected for implementation, please ensure your Feature Request meets the following requirements.
+
+
+ - 🔍 **Search for similar Feature Requests before opening a new one.** Avoid duplicates and save time by **[using the filters at the top of the Feature Requests list](https://elemn.to/gh-feature-requests)** to narrow your search.
+
+ - 🗳️ **Vote for existing Feature Requests.** Instead of opening a new discussion or writing "+1", use the **Upvote** button to express your interest in suggested features. The most voted Feature Requests are more likely to be considered for implementation in future versions.
+
+ - ☝️ **Only one request per discussion.** Please don't bundle multiple Feature Requests in a single submission. This helps us track and prioritize features that the majority of users are interested. Discussions with bundled requests can't be considered for implementation.
+
+
+
+
🎯 Scope
(click to expand)
+
+ To keep this repository focused and efficient, there are some types of discussions that we are unable to handle here. These discussions will be **closed without further action**.
+
+
+ - 🛟 **Requests for personal support** This includes help with setup, troubleshooting, or usage guidance. For that, please contact one of our **[official Support Channels](https://elemn.to/support-ticket)**.
+
+ - 🐞 **Bug Reports and conflicts** If you're here to report issues with existing features in Elementor, please **[use our 🐞 Bug Report form instead](https://elemn.to/gh-new-bug-report)** We're only able to address issues related to Elementor and Elementor Pro directly. If the problem occurs when using a plugin, theme, or integration that is not officially supported by Elementor, please reach out to the 3rd-party provider for assistance.
+
+ - 📚 **Questions about custom code or extending Elementor.** We cannot provide assistance with writing or debugging custom code. If your goal is to extend Elementor, we recommend referring to our **[Developers Documentation](https://elemn.to/dev-docs)**.
+
+ - 🛡️ **Security and vulnerability disclosures.** We take security seriously. Please use our managed **[Bug Bounty Programs](https://elemn.to/bug-bounty)** to responsibly report security issues.
+
+ - ☹️ **Complaints or offensive content.** While we are open to feedback, this is not the appropriate place to submit complaints about Elementor's products or services. We also do not tolerate offensive, discriminatory, or hostile remarks. Please keep discussions respectful as outlined in our **[Code of Conduct](https://elemn.to/gh-code-of-conduct)**.
+
+ - ❌ **Incomplete, invalid, or out-of-scope discussions.** Discussions without clear descriptions, or unrelated to Elementor or Elementor Pro feature suggestions will be closed without further action.
+
+
+ ## 📝 Instructions
- ### 💬 Provide a Detailed Description
- - Please explain in detail what problem your idea is going to solve. (Required)
- - Describe how you'd like a solution to be implemented. (Required)
- - Give examples of alternative solutions you've considered.
- - Add context to your suggestion by providing examples, screenshots, screen recordings, related links, and additional information.
+ To help us understand and consider your request, follow these best practices:
+
+ - ✒️ **Use a clear and descriptive title.** A good title helps everyone quickly understand your suggestion and increases the chances of votes. Try to summarize the problem in a few words.
+
+ - 💬 **Describe the problem your feature would solve.** What is the pain point or limitation this feature would improve?
+
+ - 💡 **Describe your proposed solution.** How do you imagine it working?
+
+ - 🔄 **Optionally suggest alternatives or workarounds.** If you've tried other approaches, share those too.
+
+ - 🖼️ **Attach screenshots or examples.** Help us visualize your idea.
- type: textarea
id: the_problem
validations:
required: true
attributes:
- label: "What problem is your feature request going to solve? Please describe.."
- description: "Help everyone understand in detail what problems you are trying to solve."
- placeholder: "I'm always frustrated when ..."
+ label: "Describe the Problem"
+ description: "What problems are you experiencing? Help everyone understand in detail what problems you encountered that could be solved by your suggestion."
+ placeholder: "Example: \nI'm always frustrated when ..."
+ - type: markdown
+ attributes:
+ value: |
+
- type: textarea
id: the_solution
validations:
required: true
attributes:
- label: "Describe the solution you'd like."
- description: "Help everyone understand in a clear and concise description what you want to happen."
- placeholder: "It would be nice if ..."
- - type: textarea
- id: alternatives
+ label: "Propose a Solution"
+ description: "Help everyone understand in a clear and concise description what solution would you like to be implemented."
+ placeholder: "Example: \nIt would be nice if we could ..."
+ - type: markdown
attributes:
- label: "Describe alternatives you've considered."
- description: "Give examples of any alternative solutions or features you've considered."
- placeholder: "It can also be solved by ..."
+ value: |
+
- type: textarea
id: additional_context
attributes:
- label: "Additional context"
- description: "Add any other context, references, or illustrations about the feature request here."
- placeholder: "Here's an example of ..."
+ label: "Additional Context"
+ description: "Optional: Give examples of any alternative solutions or features you've considered, or share any other information you think should be relevant."
+ placeholder: "Examples: \nIt can also be solved by ... \nHere's an example of ... \nDrag and drop your attachments here:"
- type: markdown
attributes:
value: |
-
- ### 📃 Agreement
- - ⚠️ Please follow all the instructions above and fill in all the required fields with valid information. We reserve the right to close requests that do not comply with these guidelines without any action.
- type: checkboxes
id: final_agreement
attributes:
label: "Agreement"
+ description: "By submitting this request, you confirm that you have read and followed all the guidelines, requirements, scope, and instructions outlined above, and you agree your discussion may be closed without further action if it doesn't meet them."
options:
- - label: "I agree that my request may be closed without action if it doesn't meet all the requirements."
+ - label: "I confirm I have read and followed all the guidelines and instructions outlined in the Feature Request form."
required: true
- - type: markdown
- attributes:
- value: |
-
-
- ---
- ### Thank you for contributing and helping shape the future of Elementor! 🙏
-
- We are thrilled to receive your request, and we will consider adding it to our [Roadmap](https://elemn.to/gh-to-roadmap) if we see enough demand from other users.
-
- _Please understand that due to the high volume of requests we receive and our commitment to continuous improvement, we can't guarantee that every suggestion will be implemented. We will, however, continue to monitor every submission. Thank you for understanding!_
+ - label: "I agree that my discussion may be closed without further action if it doesn't meet all the requirements outlined in the Feature Request form."
+ required: true
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/bug.yml b/.github/ISSUE_TEMPLATE/bug.yml
index 950649d01468..3947933ddce8 100644
--- a/.github/ISSUE_TEMPLATE/bug.yml
+++ b/.github/ISSUE_TEMPLATE/bug.yml
@@ -1,142 +1,153 @@
-name: "🐞 Bug Report"
-description: "Did you find a bug in the source code of Elementor, and can reproduce it consistently after troubleshooting it? Report it here."
+name: "🐞 Report a Confirmed Bug in Elementor"
+description: "Found a reproducible bug in Elementor's source code after troubleshooting? Submit it here to help us improve."
labels: ["status/awaiting_triage"]
body:
- type: markdown
attributes:
value: |
- **👋 Hello, welcome to the Elementor Bug Reports!**
- # ⚠️ BEFORE POSTING READ THIS CAREFULLY
- ## 🐞 Please only use this form to report validated Elementor Bugs.
- ### 🛟 Need Help, Guidance, Assistance, or Support? [Click here to get support](https://elemn.to/support-ticket).
- ### 🔧 Before submitting your issue, troubleshoot and validate it. [Click here to start troubleshooting](https://elemn.to/help-troubleshooting).
-
- **ℹ️ For more information please read our [Contribution Guidelines](https://elemn.to/gh-contributing).**
+ # 🐞 Report a Confirmed Bug in Elementor
- ### 😉 Follow these best practices to help save time
- - ✒️ **Write a Clear and Concise Title** Summarize your title in a short sentence that can help identify your issue at a glance without needing to read the description.
- - ☝️ **One Bug per Thread** If you are experiencing more than one bug, submit only **ONE BUG PER ISSUE**. Issues with more than one reported bug may be closed without action.
+ 👋 **Hello, welcome to Elementor's repository!**
+
+ Thank you for contributing - your input helps make **Elementor** better for everyone!
+ ## 🧭 Guidelines
- ### ✳️ All fields are required!
- - ❌ Issues lacking detail or submitted for any other reason than to report Elementor-specific bugs may be closed without action.
- - 🧩 We do not provide solutions for 3rd-party add-ons, extensions, and other plugins or themes that Elementor does not offer official integration.
+ Before getting started, please take a moment to review our **[Contribution Guidelines](https://elemn.to/gh-contributing)** and **[Code of Conduct](https://elemn.to/gh-code-of-conduct)**. These help us keep this space organized, respectful, and inclusive for everyone.
- ## THE ISSUE
- ### 📋 Prerequisites
- - 🔍 **Search Before Posting** Please **[search for similar issues](https://elemn.to/gh-issues)** (both open and closed) to prevent creating duplicates. Use **[GitHub Labels](https://elemn.to/gh-labels)** to refine your search.
- - 🆕 **Stay Up-to-date** Ensure you are using the **[most recent and stable versions](https://elemn.to/changelog)** of Elementor (and Elementor Pro), as well as all installed plugins, themes, and WordPress.
- - type: checkboxes
- id: prerequisites
- attributes:
- label: "Prerequisites"
- options:
- - label: "I have searched for similar issues in open and closed tickets and cannot find a duplicate."
- required: true
- - label: "I have troubleshooted my issue, and it still exists against the latest stable version of Elementor."
- required: true
- - type: markdown
- attributes:
- value: |
+ > [!IMPORTANT]
+ > ### 🐞 This form is specifically for reporting confirmed Elementor bugs.
+ > **We welcome your input, but please only use this form if you've already investigated and validated that the issue is caused by Elementor itself.**
+ >
+ > For Personal Help, Assistance or Support, please use one of our **[🛟 Personal Support Channels](https://elemn.to/support-ticket)** instead.
+ >
+ > Take a look at the 🎯 **Scope** section below to understand which types of reports are not handled here.
+ >
+ > ⚠️ _**Submitting unrelated or incomplete issues may result in them being closed without further action.**_
+
+
+
+
📋 Requirements
(click to expand)
+
+ For a quick review and efficient resolution, please ensure your report meets the following requirements.
+
+
+ - *️⃣ **All fields in this form are required** - no exceptions. Incomplete issues will be closed without further action.
+
+ - 🔍 **Search for similar issues before opening a new one.** Avoid duplicates and save time by using the filters at the top of the **[Issues list](https://elemn.to/gh-issues)** to narrow your search.
+
+ - 🆕 **Ensure you have the latest stable versions installed.** Including Elementor, Elementor Pro, WordPress core, your active theme, and all installed plugins. 👉 Stay updated: **[Elementor Changelogs](https://elemn.to/changelog)**
+
+ - 🗑️ **Clear all relevant cache layers.** Confirm the issue is not being caused by old cached data. Please clear server cache, site-level cache (including plugin-based cache), CDN cache, and your browser cache - in that order to avoid possible cache conflicts.
+
+ - 🕵️ **Test with only Elementor, Elementor Pro, and the Hello Theme active.** Temporarily disable all other plugins and themes. This step helps confirm that the issue is not being caused by a 3rd-party conflict. 👉 Reference: **[Troubleshooting the Editor](https://elemn.to/help-troubleshooting)**
+
+ - 💾 **Copy and paste your complete Elementor System Info.** This is not optional. It helps us better reproduce and understand your issue. Reports without the full Elementor System Info will be closed. 👉 Learn how to copy it here: **[Share system information with Elementor](https://elemn.to/help-system-info)**
+
+ - 🪪 **If you're a 3rd-party developer**, please introduce yourself. Include your name, company, product name, and a way for us to contact you (such as an email address) if needed. This helps us collaborate more effectively.
+
+ - ☝️ **Only one issue per report.** Please don't bundle multiple bugs in a single submission. This helps us track, reproduce, and fix each issue accurately.
+
+
+
+
🎯 Scope
(click to expand)
+
+ To keep this repository focused and efficient, there are some types of reports that we are unable to handle here. These issues will be **closed without further action**.
+
+
+ - 🛟 **Requests for personal support** This includes help with setup, troubleshooting, or usage guidance. For that, please contact one of our **[official Support Channels](https://elemn.to/support-ticket)**.
+
+ - 🧩 **Conflicts with 3rd-party plugins, themes, or services.** We're only able to address issues related to Elementor and Elementor Pro directly. If the problem occurs when using a plugin, theme, or integration that is not officially supported by Elementor, please reach out to the 3rd-party provider for assistance.
+
+ - 🚀 **Feature requests or suggestions.** We love your ideas! But this form is only for confirmed bugs. This includes missing but not supported or intended features. Please use the dedicated Feature Request form instead. See: **[Request a Feature](https://elemn.to/gh-new-feature-request)**
+
+ - 📚 **Questions about custom code or extending Elementor.** We cannot provide assistance with writing or debugging custom code. If your goal is to extend Elementor, we recommend referring to our **[Developers Documentation](https://elemn.to/dev-docs)**.
+
+ - 🛡️ **Security and vulnerability disclosures.** We take security seriously. Please use our managed **[Bug Bounty Programs](https://elemn.to/bug-bounty)** to responsibly report security issues.
+
+ - ☹️ **Complaints or offensive content.** While we are open to feedback, this is not the appropriate place to submit complaints about Elementor's products or services. We also do not tolerate offensive, discriminatory, or hostile remarks. Please keep discussions respectful as outlined in our **[Code of Conduct](https://elemn.to/gh-code-of-conduct)**.
+
+ - ❌ **Incomplete, invalid, or out-of-scope reports.** Issues without clear steps to reproduce, missing required fields, or unrelated to Elementor or Elementor Pro will be closed without further action.
+
+
+ > [!NOTE]
+ > ### 🧪 Elementor Editor V4
+ > If you are testing the new **[Editor V4](https://elemn.to/editor-v4)** features and wish to report bugs or share feedback, please use one of the forms below:
+ >
+ > **[🐛 Report bugs specific to Editor V4](https://elemn.to/editor-v4-new-issue)**
+ > **[🗣️ Discuss and share feedback about the Editor V4](https://elemn.to/editor-v4-feedback)**
+
+ ## 📝 Instructions
+
+ To help us understand and resolve your issue, please follow these best practices:
+
+ - ✒️ **Use a clear and descriptive title.** A good title helps everyone quickly understand what the issue is about. Try to summarize the problem in a few words.
+
+ - 💬 **Describe the issue in detail.** Include as much context as you can. What happened? When did it start? What page or feature does it affect? Feel free to attach screenshots or screen recordings - just drag and drop them into the text field when filling out the form.
+
+ - 👣 **List all steps to reproduce the issue.** Pease be specific! We need to follow the exact steps you took to reproduce the issue - ideally on a clean WordPress installation. Reports without clear reproduction steps may be closed, as we cannot fix what we cannot replicate.
- ### 💬 Provide a Detailed Description
- Please describe the problem in detail, provide examples, screenshots, and related links.
+ - 🧠 **Explain what you expected to happen.** Help us understand what you believe the correct or intended behavior should be.
- type: textarea
id: description
validations:
required: true
attributes:
label: "Description"
- description: "Please help us understand in detail what problems you are experiencing."
+ description: "Describe the issue in detail and include as much context as possible.
Feel free to attach screenshots or screen recordings - just drag and drop them into the field below."
+ placeholder: "Please be thorough. What happened? When did it start? What page or feature does it affect? \n\nThe more information you share, the quicker we can find a solution! \n\nDrag and drop your attachments here:"
- type: markdown
attributes:
value: |
-
- ### 👣 Steps to Reproduce
- Enumerate all the steps needed to reproduce the issue in detail so we can replicate it in our environment.
- - Be thorough. We will only be able to reproduce your issue if you thoroughly explain all the steps to replicate it.
- - Please **share a screen recording**. It helps a lot!
- type: textarea
id: steps_to_reproduce
validations:
required: true
attributes:
label: "Steps to reproduce"
- description: "Provide steps that we can recreate on our own."
- placeholder: "1. ... \n2. ... \n3. ..."
+ description: "List all steps to reproduce the issue. Be specific!
We need to follow the exact steps you took to reproduce the issue - ideally on a clean WordPress installation."
+ placeholder: "Example: \n1. In the WordPress Dashboard, go to... \n2. Create a Template... \n3. Drag & Drop the element... \n4. ..."
- type: markdown
attributes:
value: |
-
- ### 🧐 Expected Behavior
- Describe the expected behavior to help identify the root of the issue.
- type: textarea
id: expected_behavior
validations:
required: true
attributes:
label: "Expected behavior"
- description: "Please help us understand what you are expecting to happen."
- placeholder: "1. ... \n2. ... \n3. ..."
- - type: markdown
- attributes:
- value: |
-
-
- ### 🕵️ Isolate the problem and Validate your issue
- - Deactivate all plugins _**except Elementor (and Elementor Pro)**_, and temporarily change the theme to the **[Hello Elementor theme](https://wordpress.org/themes/hello-elementor/)**.
- - Verify if your problem happens when only the Elementor (and Elementor Pro) plugins are active while also using the Hello Elementor theme.
- - If the issue can't be recreated consistently or reproduced following the steps above, it's likely **not an Elementor bug**. In that case, use the **[support link](https://elemn.to/support-ticket)** at the top of this form, or **[troubleshoot your issue again](https://elemn.to/help-troubleshooting)**.
- - type: checkboxes
- id: isolating_the_problem
- attributes:
- label: "Isolating the problem"
- options:
- - label: "This bug happens when only the Elementor (and Elementor Pro) plugins are active."
- - label: "This bug happens with the Hello Elementor theme active."
- - label: "I can reproduce this bug consistently by following the steps I described above."
+ description: "Explain what you expected to happen.
Help us understand what you believe the correct or intended behavior should be. This way we can identify the root of the issue quickly and find a solution faster."
+ placeholder: "Examples: \nAccording to the Documentation in the Help Center I expected... \nWhen I apply a style to an element I expect it to... \nWhen I visit a page in the fontend, I expect..."
- type: markdown
attributes:
value: |
-
- ### 💾 Elementor System Info
- **⚠️ This field is REQUIRED**
- - Please copy and paste the **full Elementor System Info** report from your WordPress **`Dashboard`** > **`Elementor`** > **`System Info`** page (available at the bottom of the page). **We won't accept issues without it. [Learn how to copy it here](https://elemn.to/help-system-info).**
- type: textarea
id: system_info
validations:
required: true
attributes:
label: "Elementor System Info"
- description: "Redact or remove sensitive information (admin email, website links, or root paths) if necessary. Keep other details, as these are vital for understanding your problem and recreating it correctly."
+ description: "⚠️ This field is required and is not optional.
Redact or remove sensitive information (like admin email, or root paths) if necessary. Keep other details, as these are vital for understanding your problem and recreating it correctly.
To learn how to copy and paste the full report visit https://elemn.to/help-system-info."
placeholder: "== Server Environment == \n== WordPress Environment == \n== Theme == \n== User == \n== Active Plugins == \n== Elements Usage == \n== Settings == \n== Features == \n== Integrations == \n== Elementor Experiments == \n== Log == \n== Elementor - Compatibility Tag == \n== Elementor Pro - Compatibility Tag =="
render: txt
- type: markdown
attributes:
value: |
-
- ### 📃 Agreement
- ⚠️ **Please follow all the instructions above** and fill in all the required fields with valid information.
- ⛔ **As a gentle reminder, we may close issues that do not comply with these guidelines without action.**
- type: checkboxes
id: final_agreement
attributes:
label: "Agreement"
+ description: "By filling out this form, you confirm that you have read and followed all the guidelines, requirements, scope, and instructions outlined above, and you agree that your issue may be closed without further action if it doesn't meet them."
options:
- - label: "I agree that my issue may be closed without action if it doesn't meet all the requirements."
+ - label: "I confirm I have read and followed all the guidelines and instructions outlined in the Elementor Bug Report form."
+ required: true
+ - label: "I agree that my issue may be closed without further action if it doesn't meet all the requirements outlined in the Elementor Bug Report form."
required: true
- - type: markdown
- attributes:
- value: |
-
-
- ---
- ### 🙏 Thank you for contributing and helping make Elementor better.
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 0464e12034f2..bc4ccd093697 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,32 +1,20 @@
blank_issues_enabled: false
contact_links:
- - name: 🛟 Get Support
+ - name: 🛟 Get Personal Support
url: https://elemn.to/support-ticket
- about: Need Help, Guidance, Assistance, or Support? Follow these instructions.
- - name: 📖 Contributing Guidelines
+ about: Need help, guidance, or personal support? Follow these steps to get assistance from Elementor Support.
+ - name: 🚀 Feature Requests
+ url: https://elemn.to/gh-feature-requests
+ about: Have an idea to improve Elementor? Submit your feature request here.
+ - name: 🧪 Editor V4 Discussions
+ url: https://elemn.to/editor-v4-feedback
+ about: Share your feedback, ideas, and thoughts about Editor V4's features.
+ - name: 📚 Visit the Developers Center
+ url: https://elemn.to/dev-center
+ about: Get technical documentation and resources to extend Elementor with custom code and integrations.
+ - name: 📖 Contribution Guidelines
url: https://elemn.to/gh-contributing
- about: Before filing a bug report, a feature request, or sending pull requests, read the Contribution Guidelines.
+ about: Before submitting a bug report, feature request, or pull request, please read our Contribution Guidelines.
- name: 🤝 Code of Conduct
url: https://elemn.to/gh-code-of-conduct
- about: To foster a safe, open, and welcoming environment, we have a Code of Conduct that all participants should follow.
- - name: 🚩 Elementor Roadmap
- url: https://elemn.to/gh-to-roadmap
- about: Before submitting a request, visit the Elementor Roadmap and learn about the status of upcoming or newly-released features.
- - name: 🚀 Feature Request
- url: https://elemn.to/gh-new-feature-request
- about: Suggest new ideas, features, or enhancements for the Elementor plugin.
- - name: 📑 Help Center
- url: https://elemn.to/gh-to-help-center
- about: Visit our Help Center to find solutions to the most frequent problems or learn how to use Elementor's many features.
- - name: 🎓 Elementor Academy
- url: https://elemn.to/gh-to-academy
- about: Grow your Web Creator skills and learn how to make the most of Elementor.
- - name: 🗨️ Elementor Global Community
- url: https://elemn.to/community-on-fb
- about: The main Facebook group is where all kinds of users come together to help each other.
- - name: 📚 Elementor Developers Center
- url: https://elemn.to/gh-to-dev-center
- about: Technical information and Elementor Developers documentation. Learn everything about extending Elementor.
- - name: 🌐 Elementor Developers Community
- url: https://elemn.to/dev-community
- about: Share tips, tricks, and knowledge with other developers about extending and developing for Elementor.
+ about: Help us maintain a safe, open, and welcoming environment by following our Code of Conduct.
diff --git a/.github/ISSUE_TEMPLATE/editor-v4-bug.yml b/.github/ISSUE_TEMPLATE/editor-v4-bug.yml
new file mode 100644
index 000000000000..7fa777ed25c9
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/editor-v4-bug.yml
@@ -0,0 +1,147 @@
+name: "🐛 Report a Confirmed Bug in Editor V4"
+description: "Report confirmed bugs in Editor V4's features and help us improve the experience before the final release."
+labels: ["status/awaiting_triage", "product/editor-v4"]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ # 🐛 Report a Confirmed Bug in Editor V4
+
+
+ 👋 **Welcome, and thank you for helping shape the future of Elementor!**
+
+ We're excited to introduce the **Editor V4** - a refreshed foundation for the Elementor Editor that improves performance, responsiveness, and workflow experience.
+
+ Your feedback is incredibly valuable. Use this form to report bugs related to Editor V4's features. Every report helps us create a better product before its full release.
+
+
+ ## 🧭 Guidelines
+
+ Before getting started, please take a moment to review our **[Contribution Guidelines](https://elemn.to/gh-contributing)** and **[Code of Conduct](https://elemn.to/gh-code-of-conduct)**. These help us keep this space organized, respectful, and inclusive for everyone.
+
+
+ > [!IMPORTANT]
+ > ### 🐛 This form is for reporting confirmed bugs in Editor V4 features only.
+ > **We welcome your input, but please only use this form if you've already investigated and confirmed that the issue is caused specifically by Editor V4 features.**
+ >
+ > ℹ️ Keep in mind **the Editor V4 is still a work in progress** - it may not include all existing features from Elementor V3, is subject to change or instability, and should not be used on production websites.
+ >
+ > 🧪 For discussing and sharing feedback about the **Editor V4**, please go to the dedicated Discussion Category instead: **[Discuss the Editor V4](https://elemn.to/editor-v4-feedback)**
+ >
+ > ⚠️ _**Issues that are unrelated to Editor V4 or missing required information may be closed without further action.**_
+
+
+
+
📋 Requirements
(click to expand)
+
+ For a quick review and efficient resolution, please ensure your report meets the following requirements.
+
+
+ - *️⃣ **All fields in this form are required** - no exceptions. Incomplete issues will be closed without further action.
+
+ - 🔍 **Search for similar issues before opening a new one.** Avoid duplicates and save time by using the **[editor-v4](https://elemn.to/editor-v4-issues)** label to narrow your search.
+
+ - 🗑️ **Clear all relevant cache layers.** Confirm the issue is not being caused by old cached data. Please clear server cache, site-level cache (including plugin-based cache), CDN cache, and your browser cache - in that order to avoid possible cache conflicts.
+
+ - 🕵️ **Test with only Elementor, Elementor Pro, and the Hello Theme active.** Temporarily disable all other plugins and themes. This step helps confirm that the issue is not being caused by a 3rd-party conflict. 👉 Reference: **[Troubleshooting the Editor](https://elemn.to/help-troubleshooting)**
+
+ - 💾 **Copy and paste your complete Elementor System Info.** This is not optional. It helps us better reproduce and understand your issue. Reports without the full Elementor System Info will be closed. 👉 Learn how to copy it here: **[Share system information with Elementor](https://elemn.to/help-system-info)**
+
+ - 🪪 **If you're a 3rd-party developer**, please introduce yourself. Include your name, company, product name, and a way for us to contact you (such as an email address) if needed. This helps us collaborate more effectively.
+
+ - ☝️ **Only one issue per report.** Please don't bundle multiple bugs in a single submission. This helps us track, reproduce, and fix each issue accurately.
+
+
+
+
🎯 Scope
(click to expand)
+
+ To keep this repository focused and efficient, there are some types of reports that we are unable to handle here. These issues will be **closed without further action**.
+
+
+ - 🐞 **Issues unrelated to bugs in the Editor V4.** If you're here to report issues with existing features in Elementor V3, please **[use our general 🐞 Bug Report form instead](https://elemn.to/gh-new-bug-report)**.
+
+ - 🛟 **Requests for personal support** This includes help with setup, troubleshooting, or usage guidance. For that, please contact one of our **[official Support Channels](https://elemn.to/support-ticket)**.
+
+ - 🧩 **Conflicts with 3rd-party plugins, themes, or services.** We're only able to address issues related to **Editor V4** features enable. If the problem occurs when using a plugin, theme, or integration that is not officially supported by Elementor, please reach out to the 3rd-party provider for assistance.
+
+ - 🚀 **Feature requests or suggestions.** We love your ideas! But this form is only for confirmed bugs. This includes missing but not supported or intended features. Please use the dedicated Feature Request form instead. See: **[Request a Feature](https://elemn.to/gh-new-feature-request)**
+
+ - 📚 **Questions about custom code or extending Elementor.** We cannot provide assistance with writing or debugging custom code. If your goal is to extend Elementor, we recommend referring to our **[Developers Documentation](https://elemn.to/dev-docs)**.
+
+ - 🛡️ **Security and vulnerability disclosures.** We take security seriously. Please use our managed **[Bug Bounty Programs](https://elemn.to/bug-bounty)** to responsibly report security issues.
+
+ - ☹️ **Complaints or offensive content.** While we are open to feedback, this is not the appropriate place to submit complaints about Elementor's products or services. We also do not tolerate offensive, discriminatory, or hostile remarks. Please keep discussions respectful as outlined in our **[Code of Conduct](https://elemn.to/gh-code-of-conduct)**.
+
+ - ❌ **Incomplete, invalid, or out-of-scope reports.** Issues without clear steps to reproduce, missing required fields, or unrelated to **Editor V4** will be closed without further action.
+
+
+ ## 📝 Instructions
+
+ To help us understand and resolve your issue, please follow these best practices:
+
+ - ✒️ **Use a clear and descriptive title.** A good title helps everyone quickly understand what the issue is about. Try to summarize the problem in a few words.
+
+ - 💬 **Describe the issue in detail.** Include as much context as you can. What happened? When did it start? What page or feature does it affect? Feel free to attach screenshots or screen recordings - just drag and drop them into the text field when filling out the form.
+
+ - 👣 **List all steps to reproduce the issue.** Pease be specific! We need to follow the exact steps you took to reproduce the issue - ideally on a clean WordPress installation. Reports without clear reproduction steps may be closed, as we cannot fix what we cannot replicate.
+
+ - 🧠 **Explain what you expected to happen.** Help us understand what you believe the correct or intended behavior should be.
+ - type: textarea
+ id: description
+ validations:
+ required: true
+ attributes:
+ label: "Description"
+ description: "Describe the issue in detail and include as much context as possible.
Feel free to attach screenshots or screen recordings - just drag and drop them into the field below."
+ placeholder: "Please be thorough. What happened? When did it start? What page or feature does it affect? \n\nThe more information you share, the quicker we can find a solution! \n\nDrag and drop your attachments here:"
+ - type: markdown
+ attributes:
+ value: |
+
+ - type: textarea
+ id: steps_to_reproduce
+ validations:
+ required: true
+ attributes:
+ label: "Steps to reproduce"
+ description: "List all steps to reproduce the issue. Be specific!
We need to follow the exact steps you took to reproduce the issue - ideally on a clean WordPress installation."
+ placeholder: "Example: \n1. In the WordPress Dashboard, go to... \n2. Create a Template... \n3. Drag & Drop the element... \n4. ..."
+ - type: markdown
+ attributes:
+ value: |
+
+ - type: textarea
+ id: expected_behavior
+ validations:
+ required: true
+ attributes:
+ label: "Expected behavior"
+ description: "Explain what you expected to happen.
Help us understand what you believe the correct or intended behavior should be. This way we can identify the root of the issue quickly and find a solution faster."
+ placeholder: "Examples: \nAccording to the Documentation in the Help Center I expected... \nWhen I apply a style to an element I expect it to... \nWhen I visit a page in the fontend, I expect..."
+ - type: markdown
+ attributes:
+ value: |
+
+ - type: textarea
+ id: system_info
+ validations:
+ required: true
+ attributes:
+ label: "Elementor System Info"
+ description: "⚠️ This field is required and is not optional.
Redact or remove sensitive information (like admin email, or root paths) if necessary. Keep other details, as these are vital for understanding your problem and recreating it correctly.
+ %2$s',
+ esc_html__( 'Here’s where you can export this website as a .zip file, upload it to the cloud, or start the process of applying an existing template to your site.', 'elementor' ),
+ esc_html__( 'Learn more', 'elementor' ),
+ );
+ ?>
+