symfony-cmf / simple-cms-bundle

UNMAINTAINED - A more-than-simple cms based on the cmf components
http://cmf.symfony.com/
49 stars 45 forks source link

Symfony 3+ compatibility #159

Open fabriciojs opened 5 years ago

fabriciojs commented 5 years ago

I have this bundle used on a Sonata/CMF project, which I am trying to get upgraded from Symfony 2.8 to 3.4 (to eventually hopefully get it to 4.0).

I see it is abandoned for a while now, while other core bundles continue to be updated. So I guess I very much would like an educated suggestion on how to approach this.

My project heavily depends on since all our pages inherits from Symfony\Cmf\Bundle\SimpleCmsBundle\Doctrine\Phpcr\Page (and Sonata admin pages inherits from Symfony\Cmf\Bundle\SimpleCmsBundle\Admin\PageAdmin. That is pretty much what is used from that bundle.

I am looking my alternatives:

  1. Getting this bundle upgraded. I am testing forking and generate a new composer.json with symfony/framework-bundle:>3.0, I get the full set of dependencies installed upon it, but I can't get any testes to run (they basically fail with:
➜  simple-cms-bundle git:(upgrade) ✗ ./vendor/bin/phpunit -vvv
PHPUnit 7.5.4 by Sebastian Bergmann and contributors.

Runtime:       PHP 7.1.19
Configuration: /Users/fabriciojs/Projects/SMS/simple-cms-bundle/phpunit.xml

[]

[Symfony SimpleCmsBundle Test Suite]
EEEEEEE.EE

[PHPCR] Error when initializing dbal:

(any directions on this if possible, very much appreciated)

  1. I might try to refactor out of that bundle Page/Route class, basically rewriting its functionality within my project.

On both of these scenarios I will have to dig further on all related packages version upgrades, which is fun but I guess very much out of scope for my specific project case.

Does anyone have some tips or different ideas on this? Any suggestion on the best approach?

Thanks very much in advance!

dbu commented 5 years ago

as stated in the readme file, this bundle is unmaintained due to lacking resources in the cmf team. if you still want to dig into it, i am ok to merge a pull request to update the bundle, but i can't spend time digging into it. if you need the combination of route and content that the bundle offers, i guess its about the same effort to update this bundle as it is to understand enough how it works that you can integrate it into your project.