Hi,

On my local MAMP stack, i ran composer update, did a dev build an all was ok. Since i don't have composer on my shared hosting. I usually deploy my code with the synchronise function of APTANA (the ide i use). Never had any problems with this (there are about 80 websites that i manage). Now when i synchronise and do a dev build on the live server i get this "there are two files containing the "blogentry" class...." Database doesn't get build. Manually removing these duplicate php files (which do exist on my local MAMP stack too without any problem) solves the problem and makes the site accesiible again, but the blog module is not updated.

Can anybody help me out.
Thanks. Guy

Could be differences in PHP version causing that.
It used to be an issue in 2.4 - but the 3.x manifest works differently & two conflicting classes became less of an issue.

Finding out why composer has put two classes of the same thing is probably the more pertinent issue.
Perhaps you've accidentally installed both blog (old 'official') and blogger (new 'official')?

Thanks for your reply Pyromanik.
I checked the PHP version. On my local machine it's 5.3, on the live server it's 5.4.
Is there something i can do besides reverting the live server to Php 5.3?

I said 'could be' ;) I'm not sure. It could be a configuration issue...

Did you check composer isn't pulling in both blog modules?

No, it's just pulling in "silverstripe/blog": "*" ... and if i change the php version on my mamp stack to php5.4, it's giving me the same error. Reverting it back solves the problem, but i guess there must be another option to solve this too.

You said there are duplicate PHP files so the error does seem valid - so as Pyromanik pointed out it's probably better to focus on working out why those duplicate files are showing up rather than which version of PHP throws an error. What are the files called that contain the duplicate files? Can you find them both if you browse the code at github?

It seems like you're not ending up with the right set of files installed for that module. Maybe try clearing your Composer cache https://getcomposer.org/doc/03-cli.md#clear-cache and updating again? And if that doesn't help, maybe try downloading the module directly from github and installing that way?

Thanks for the replies y'all!
I solved it by first deleting the blog module (using composer) on my dev version. Then i updated the live site. At that point, there was no blog anymore.
Next, i added the blog module again (using composer) on my dev version, synchronised with my live site and everything is working again.

I don't know exactly what went wrong earlier. My guess is that some files weren't deleted on the live site when syncing the first time and were "synced back" to my development version.