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

Symfony 2.5 support #26

Open
kikegarcia opened this issue Jun 5, 2014 · 6 comments
Open

Symfony 2.5 support #26

kikegarcia opened this issue Jun 5, 2014 · 6 comments

Comments

@kikegarcia
Copy link

Hi,

Are there any plans to port this bundle to 2.5 or it would be better for me to downgrade my Symfony? Composer updated to it automaticaly, but now I don't know what to do, I really need this bundle.

Thanks!

@reecefowell
Copy link
Member

Hi @kikegarcia if you know what is required for 2.5 then you can send me a PR and i will happily support 2.5 as i am not able to commit any time to CCDN stuff right now due some new projects i am working on.

Thanks for your interest, i appreciate it.

@ghost
Copy link

ghost commented Jun 26, 2014

check #29

@ikerib
Copy link

ikerib commented Nov 26, 2014

I´ve got this error with a fresh install

Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for codeconsortium/ccdn-forum-bundle dev-master -> satisfiable by codeconsortium/ccdn-forum-bundle[dev-master].
- codeconsortium/ccdn-forum-bundle dev-master requires symfony/symfony 2.4.* -> no matching package found.

Potential causes:

@smilesrg
Copy link

smilesrg commented Mar 4, 2015

@ikerib I have no such issue. You can try:
php composer.phar require "codeconsortium/ccdn-forum-bundle":"@dev"

@joschi127
Copy link
Contributor

Symfony 2.5 and 2.6 support (2.7 not tested yet) was added by PR #39.

However there is no stable release tagged yet to use it so you have to use the dev version as already spotted by @smilesrg .

@joschi127
Copy link
Contributor

@reecefowell Should we tag a 2.1.0 release?

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

No branches or pull requests

5 participants