Closed (fixed)
Project:
Simplenews
Version:
8.x-1.x-dev
Component:
User interface
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Jul 2015 at 14:25 UTC
Updated:
18 Aug 2015 at 12:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
edurenye commentedComment #2
edurenye commentedSolved, now the link is shown properly.
Comment #3
berdirI don't think that's correct, unless we actually cache those per language now and afaik we don't?
Support for title arguments was removed from core, although I don't fully understand the reason, this was the perfect example that needs it :)
Comment #4
alexpotttitle arguments support was removed from YamlDiscovery of plugins. This is a derived plugin afaik that is a totally different situation.
Comment #5
berdirApparently not, because the title argument is clearly no longer available here. It's using the same class as local actions defined in yaml, so it has the same features.
I guess we need a custom local task plugin class to support this :(
Comment #6
miro_dietikerWell there is also the core guideline that proposes to only have one such item... Currently we create multiple in case there are multiple newsletter types...
So... Do we need an intermediate page in case there are multiple newsletter types?
Workaround proposal to deal with the situation:
In case we have only one type we could directly point the user to the node creation form.
In case we have multiple types, we should just point the user to the "Add content" overview...
Comment #7
edurenye commentedDone, now it differs from only type and multiple types.
Comment #14
juanse254 commentedIts green now, everything is looking good.
Comment #15
berdirHardcoding that type is wrong, instead, you need to use reset($node_types) if you just have one.
Calling t() here is wrong, it will not work correctly for transltable sites.
Still not sure what the correct solution is, maybe using a TranslationWrapper().
Same, t() is wrong.
Also, add content is wrong and that list will then show all the types, not sure I like that pattern.
I'd actually suggest to just do the minimal (correct) fix here to get the tests passing again and then think about the multiple local actions problem in a separate issue.
Comment #16
edurenye commentedDone.
Comment #17
edurenye commentedI forgot the translatorwrapper.
Comment #18
berdirOk, committed for now, not sure this is correct but we can change later and it works.