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

WIP Re-add Neos7 Flicker plugin for testing the fusion plugin #190

Draft
wants to merge 2 commits into
base: 9.0
Choose a base branch
from

Conversation

mhsdesign
Copy link
Member

This should not be merged but as we have no real test otherwise if the plugins work and if they should be part of 9.0 we have to test them $somehow.

I used the NeosDemo 7.3 Flicker plugin under the assumption that it should work.

@mhsdesign mhsdesign marked this pull request as draft February 21, 2024 10:05
Classes/Controller/FlickrController.php Outdated Show resolved Hide resolved
Comment on lines +18 to +24
options:
# todo weren't plugin views removed? https://github.com/neos/neos-development-collection/pull/4330
'pluginViews':
'UserFeed':
label: 'Neos.Demo:NodeTypes.Content.Flickr:options.pluginViews.userFeed'
controllerActions:
'Neos\Demo\Controller\FlickrController': ['userStream']
Copy link
Member Author

Choose a reason for hiding this comment

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

is this dead code?

Copy link
Member

@kitsunet kitsunet Feb 21, 2024

Choose a reason for hiding this comment

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

pluginViews? Yeah we removed those. Which technically means we broke this plugin, because people said no one ever uses plugin views 🙈

<li class="pull-left">
<f:render partial="Flickr/Photo" arguments="{photo: photo}" />
<p>
<f:link.action action="userStream" arguments="{userId: photo.author_id}">Show more photos by "{photo.author}"</f:link.action>
Copy link
Member Author

Choose a reason for hiding this comment

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

that link cannot be resolved:

Could not resolve a route and its corresponding URI for the given parameters. This may be due to referring to a not existing package / controller / action while building a link or URI. Refer to log and check the backtrace for more details

arguments:

{
  "node": "live__eyJsYW5ndWFnZSI6ImVuX1VTIn0=__336d96a5-b6c6-7d81-685f-89d32c37756e",
  "@package": "Neos.Neos",
  "@controller": "Frontend\\Node",
  "@action": "show",
  "@format": "html",
  "--neos_demo-content_flickr": {
    "@package": "neos.demo",
    "@controller": "flickr",
    "@action": "userstream",
    "@format": "html",
    "userId": "187194180@N06"
  }
}

Copy link
Member

@kitsunet kitsunet Feb 21, 2024

Choose a reason for hiding this comment

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

Is "node" in this a correct representation for a frontend node in a route?
The rest seems fine to me...

Copy link
Member Author

Choose a reason for hiding this comment

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

ah checked out the actual 7.3 demo and it seems the way this plugin was engineered it somehow realied on plugin views .. thats probably why it wont work?

The "master" page
image

structure
image

"plugin" page

image

Copy link
Member

Choose a reason for hiding this comment

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

could be, but in theory it should just be able to link to the page and switch to this action then. like views were never needed for multiple actions, just if you wanted to split those actions to different pages.

Copy link
Member Author

Choose a reason for hiding this comment

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

i dont understand ... not even linking to the same page works:

public function tagStreamAction()
{
    return $this->uriBuilder->uriFor('tagStream');

Copy link
Member Author

Choose a reason for hiding this comment

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

oh wait a second ... i think i answered

Is "node" in this a correct representation for a frontend node in a route?

to quickly in my head node is usually a node address object i think. And yess 💯 now the links resolve :D

Copy link
Member Author

@mhsdesign mhsdesign Feb 22, 2024

Choose a reason for hiding this comment

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

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.

None yet

2 participants