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

Move and namespaces legacy fields #17322

Closed
wants to merge 4 commits into from

Conversation

fastslack
Copy link
Contributor

@fastslack fastslack commented Jul 28, 2017

Summary of Changes

This change move legacy form fields to Joomla\CMS\Form\Field directory for namespaces

Testing Instructions

Use Category , ComponentLayout or ModuleLayout form field and should work as usual

Expected result

Work as usual

@@ -82,7 +86,7 @@ protected function getOptions()
* unless the item is already in that category.
* Unset the option if the user isn't authorised for it. In this field assets are always categories.
*/
if ($user->authorise('core.create', $extension . '.category.' . $option->value) === false)
if ($user->authorise('core.create', $extension . '.category.' . $option->value) != true)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

!==

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Contributor

@mbabker mbabker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs class mapping.

@wilsonge
Copy link
Contributor

wilsonge commented Aug 5, 2017

Do we want the category form field to be moved into the category component rather than being a library form field?

use Joomla\CMS\Factory;
use Joomla\CMS\Form\Form;
use Joomla\CMS\Form\FormField;
use Joomla\CMS\Filesystem\Folder;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These haven't been namespaced yet

use Joomla\CMS\Factory;
use Joomla\CMS\Form\Form;
use Joomla\CMS\Form\FormField;
use Joomla\CMS\Filesystem\Folder;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

@joomla-cms-bot joomla-cms-bot changed the title Move and namespaces legacy fields Move and namespaces legacy fields Nov 1, 2017
@ghost
Copy link

ghost commented Nov 1, 2017

Status is set on "Needs Review".

@fastslack
Copy link
Contributor Author

Should I do same thing but for 3.9 branch and close this PR?

@ghost ghost added the J3 Issue label Apr 5, 2019
@ghost ghost removed the J3 Issue label Apr 19, 2019
@Quy
Copy link
Contributor

Quy commented Jun 15, 2019

@wilsonge Close PR?

*
* @copyright Copyright (C) 2005 - 2017 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @copyright Copyright (C) 2005 - 2017 Open Source Matters, Inc. All rights reserved.

This comment was marked as abuse.

*
* @copyright Copyright (C) 2005 - 2017 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @copyright Copyright (C) 2005 - 2017 Open Source Matters, Inc. All rights reserved.

This comment was marked as abuse.

*
* @copyright Copyright (C) 2005 - 2017 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @copyright Copyright (C) 2005 - 2017 Open Source Matters, Inc. All rights reserved.

This comment was marked as abuse.

@laoneo
Copy link
Member

laoneo commented Mar 18, 2022

Sorry that it has taken so long to respond to this pull request. We did this change in Joomla 4 already and wont move the files in Joomla 3. So I'm closing this pr. Nevertheless we would like to thank you for your contribution.

@laoneo laoneo closed this Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants