-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[4.3] Backporting changes from framework Input/Cookie class to CMS class #40414
Conversation
I have tested this item ✅ successfully on e33f299 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40414. |
Adding screen shot for the cookie being 1 year out. This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40414. |
I have tested this item ✅ successfully on e33f299 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40414. |
Thank you for this patch. Super 👍🏽😊🙏🏽 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40414. |
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/40414. |
Thank you Hannes @Hackwar for the fix! |
Pull Request for Issue #40412 .
Summary of Changes
This PR backports several bugfixes from the frameworks Input/Cookie class to the CMS class, making the classes compatible. This fixes the issue of the languagefilter not being able to set the cookie. The original issue is, that our base class for our application, AbstractWebApplication, defines the Input object as the framework class, while the child classes use the CMS class instead.
Testing Instructions
Actual result BEFORE applying this Pull Request
Expected result AFTER applying this Pull Request
Link to documentations
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed