1

On a new project I have to upgrade a old typo3 installation from 4.2 to 6.2 or even 7.6.

The big problem is, that everything is done with templavoila and all extensions are pibased.

I learned with typo3 6.x all pibased extensions will die. But with my research now I found out that pibased extensions can still run in newer typo3 versions.

My question now is, is it smart to stay with pibased extensions and templavoila? The alternative is to create the page new with extbase and fluid-templates new from scratch. Or is there a better way?

The last thing is I will have to maintain this page and I have not much knowledge in templavoila. I also understand extbase extensions much better than pibased ones. But the time difference between keeping everything with pibase and templavoila and creating the whole page from scratch is months.

So I am not sure which way I shall suggest. What are your experiences?

Andrew
  • 585
  • 4
  • 17
nbar
  • 6,028
  • 2
  • 24
  • 65

2 Answers2

2

On TYPO3 ver. 6.x some pibased extension may work - after fixing some things. I don't remember status of TemplaVoila, but it's rather not optimistic on 6.1+

On ver. 7.x they won't work anymore! most of 4.x API methods was removed and replaced with new ones (6.x were the last versions where they was marked as depreciated but still available)

So, staying with pibase and TemplaVoila is dead-end-street, you have no choice - if you want to upgrade TYPO3 version, you need to create it from the scratch. Good news is that creating extensions with Extbase/Fluid etc is much more effective than pibase, bad news is that you will need to move the content manually. If you have big instance create new site first then consider writing the data converter... If it's rather small one just spend several hours to copy-paste the content to the new one.

biesior
  • 55,576
  • 10
  • 125
  • 182
  • There is a version of TemplaVoila available for 6.2, I'm successfully using it in one site. Don't know where I got it from though, might be some GitHub Repo. – Jost Feb 17 '16 at 06:05
  • Just to mention: there is an [EXT:compatibility6](https://typo3.org/extensions/repository/view/compatibility6), which makes old pibase code work in TYPO3 7. But I wouldn't recommend using it on a long term, bcs you simply get no speed boost benefits of T3 7 with this extension enabled. – Viktor Livakivskyi Feb 17 '16 at 10:24
  • 1
    You will still find all the missing API calls in the extension [div2007](https://typo3.org/extensions/repository/view/div2007) which uses the same Migrations as in TYPO3 6.2. So most TYPO3 extension will work without any adaptions. Or the only modification which must be done is: remove the include_once statements and create the file ext_autoload.php . You recommendation to use Extbase/Fluid is misleading. – Franz Holzinger Feb 22 '16 at 19:46
  • @FranzHolzinger Great to know anyway I can't find any logical reason to use new TYPO3 versions with old extension, or vice versa ;) I have several instances under maintenance-mode created many years ago, which uses old APIs and they just works, no need to update the core. There's no reason to update the TYPO3 if whole stuff is done with 3.x or 4.x approach and works. For instances that should be done with quite new feel&look I just suggest to create them from the scratch – biesior Feb 22 '16 at 19:52
0

The TYPO3 road map at https://typo3.org/typo3-cms/roadmap/ and the TYPO3 download pages have 6.2 LTS support ending March 2017, and 7 LTS support going to November 2018. So this gives you about a year from now to keep using extensions dependent on 6.2 and develop new code at the same time. It would be good to check extension developer plans, too. I depend on at least one extension where the developer says he'll get around to a version 7, but not right now. In my opinion, Extbase is the way to go. Play with Extension Builder, to get you well on the way.

Andrew
  • 585
  • 4
  • 17