YAG and typo3 v8 LTS?

[yberton]

Hello,
Is a version for typo3 v8 planned? If so, when do you think it will be available?
thanks in advance

[outdoorsman]

I'm interested in knowing this too. Just trying to plan for a new client I have.

[daniellienert]

Hey @yberton,

I gave the answer already in #99 - as closed issues are easily overseen, I leave this one open for discussion.

Currently there is no roadmap for upgrading YAG for 8.0. As my free-time open source work is currently dedicated to Neos. Sure, I will help upgrading the gallery as soon as an customer TYPO3 8.0 project needs it.
But luckily it is open source! So I would be glad to integrate pull requests that update YAG for 8.0.

Cheers,
Daniel

[yberton]

OK @daniellienert I hope I will be soon as possible! 📦
If I have a little time, I will try to wear it on the v8 ...
See you later

[schiran]

Hi all,
I would also be interested in a YAG v8-Version. I would be willing to participate in any work to be done for that...

Cheers
Nicolai

[daniellienert]

@schiran: First thing could be to describe what the actual problems are?
Have you tried to (force) install the extension on a v8 instance? What are the first things to do?

[kdjkdjkdj]

Hint: Some changes are already in the last commits, so please use the latest git version for your tests.

And as for TYPO3 V8 PHP7 is also a pre-requirement, I have done some changes (#108) for the compatibility here. This will reduce the number of warnings dramatically.
May someone also tests this changes that it gets merged.

[Poepp]

Please see my comment to pull request #110.
Has anyone being successfull in getting YAg to work with typo3 8.7 and PHP 7.1?
I'm really looking forward to have this gallery back to work again.

[ProWebs]

Nope :(

Call to undefined method TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::getPageRenderer()

As it looks no one will make it ready vor typo3 8 has someone experience with a other extension which is equal to YAG?

[Bunnyfield]

Hi Daniel and other folks interested in having YAG officially available for CMS 8 or later.

Within our Coders.Care upgrade initiative we are currently dealing with exactly that scenario and would like to provide a working version soon. This version might not have all deprecated methods eliminated but would be working upt to PHP 7.2 on CMS 8.

AFAICS there are two other extensions that need to be upgraded too for that purpose, which are pt_extlist and pt_extbase.

We would like to get a confirmation before starting the upgrade process, so that we can make sure, the result will be published here and in the TER too, otherwise we would have to go for a fork, which is what we want to avoid.

@daniellienert maybe you could contact Petra so we could even have an official contract to support you and/or your extensions based on the extension SLAs we are providing.

Everybody have a nice week :-)

[daniellienert]

Hey @Bunnyfield,

that really sounds great! We put a lot of time and effort in this extension - and I guess some parts of it are still unique in the TER. It is fact, that I currently don't have the time (and the projects) to maintain this extension - but it would be great If someone is willing to take over!

Master of pt_extlist and pt_extbase should be fully v8 compatible already at least for our projects.

So what needs to be done next? How should I contact Petra?

Cheers,
Daniel

[Bunnyfield]

I just sent her the Github mail and put you in CC

[Bunnyfield]

BTW: ext_emconf.php of pt_extlist and pt_extbase still state "7.6.0-7.9.99", which is why they don't appear correctly in the TER. composer.json is fine though.

[schrej-zz]

Hi;
the fork of Anke is already running very well with newest branches of Punkt.de pt_extlist & pt_extbase:
https://github.com/kiwi2101/yag/tree/typo3-v8
The only issue, I still get is
#123
when selecting the "Gallery" tab of the menu in BE.
... solved in the meantime, at least as a workaround. See issue