icaplyon1 / blogbundle Goto Github PK

The bundle cannot be installed because there's two migration classes with identical content in the Migrations folder. If one of those is deleted, everything works fine.

(I've downgraded temporarily the plugin's reference in the super project, let me know when I can upgrade it again, or just send a PR)

J'ai un retour disant :
"pendant la création du blog avec Internet Explorer 9 je n'arrive pas à avoir la pop-up qui permet d'écrire le nom du blog et donc de le créé." (sur firefox ça fonctionne).

Je n'ai pas d'IE9 pour vérifier ici mais j'ai en effet constater ce genre de soucis la dernière fois que j'ai utilisé claco sur ie.

The calendar should be translated in French

L'accès à un blog depuis un lien (genre sur google +) mène parfois vers une page blanche quand on est pas authentifié sur la plateforme (http://claco.univ-lyon1.fr/forum/subject/85/messages/page)

Tag need to be a simple string in order to avoid error when filled in with an url.

To make this work the tag mechanism will be upgraded to use slug for url generating.
A new field will be add and the actual one would become the tag's label.

Post feed.

I create an article, today 11/11 and i postdate the article : i set it to 01/1. I save it like that, It is in non visible mode. If then i click on publish the article, it then appears with today's date : 11/11

Editing the "Info bar" of a blog throws the following exception :

Variable "user" does not exist in /home/stephane/php/projets/claronext/vendor/icap/blog- bundle/Icap/BlogBundle/Resources/views/layout.html.twig at line 125

Besides, the same template keeps a reference to a pre-3.x controller:

{% render controller('ClarolineCoreBundle:ResourceType:initPicker') %}
{{ tinymce_init() }}

Show list of title's posts of a blog.
When you click on a title it shows the post.

this bug appear on the installation claco (http://claco.univ-lyon1.fr) :

When adding a post to a blog, if a date is specified with the date picker we have the message : " Cette valeur n'est pas valide.".

The value in the field set by the datepicker is in format MM/DD/YYYY. The field isn't editable with out the date picker.

Display some statistics:

• 5/10/20 last comment
• Most viewed posts

When in view mode as a blog creator, there is no agenda widget, even if it is set visible in the options, when it's displayed in one column mode : in two column mode (width > 1200px) the agenda is visible.
In option mode, though, the agenda is always visible.

After upgrade of claroline core 2.1.8

"Doctrine\DBAL\DBALException" thrown with message : "An exception occurred while executing 'SELECT t0.infos AS infos1, t0.id AS id2, t3.id AS id4, t3.authorize_comment AS authorize_comment5, t3.authorize_anonymous_comment AS authorize_anonymous_comment6, t3.post_per_page AS post_per_page7, t3.auto_publish_post AS auto_publish_post8, t3.auto_publish_comment AS auto_publish_comment9, t3.banner_activate AS banner_activate10, t3.banner_background_color AS banner_background_color11, t3.banner_height AS banner_height12, t3.banner_background_image AS banner_background_image13, t3.banner_background_image_position AS banner_background_image_position14, t3.banner_background_image_repeat AS banner_background_image_repeat15, t3.blog_id AS blog_id16, t0.resourceNode_id AS resourceNode_id17 FROM icap__blog t0 LEFT JOIN icap__blog_options t3 ON t3.blog_id = t0.id WHERE t0.resourceNode_id = ? LIMIT 1' with params [21]: SQLSTATE[42S22]: Column not found: 1054 Unknown column 't3.banner_activate' in 'field list'" (500 Internal Server Error) at n/a in /home/cctest/vendor/doctrine/dbal/lib/Doctrine/DBAL/DBALException.php line 91 at Doctrine\DBAL\DBALException::driverExceptionDuringQuery in /home/cctest/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php line 701 at Doctrine\DBAL\Connection->executeQuery in /home/cctest/vendor/doctrine/orm/lib/Doctrine/ORM/Persisters/BasicEntityPersister.php line 748 at Doctrine\ORM\Persisters\BasicEntityPersister->load in /home/cctest/vendor/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php line 196 at Doctrine\ORM\EntityRepository->findOneBy in /home/cctest/vendor/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php line 241 at Doctrine\ORM\EntityRepository->__call in /home/cctest/vendor/claroline/core-bundle/Claroline/CoreBundle/Manager/ResourceManager.php line 1026 at Icap\BlogBundle\Repository\BlogRepository->findOneByResourceNode in /home/cctest/vendor/claroline/core-bundle/Claroline/CoreBundle/Manager/ResourceManager.php line 1026 at Claroline\CoreBundle\Manager\ResourceManager->getResourceFromNode in /home/cctest/vendor/claroline/core-bundle/Claroline/CoreBundle/Controller/ResourceController.php line 168 at Claroline\CoreBundle\Controller\ResourceController->openAction in line at call_user_func_array in /home/cctest/app/bootstrap.php.cache line 2815 at Symfony\Component\HttpKernel\HttpKernel->handleRaw in /home/cctest/app/bootstrap.php.cache line 2789 at Symfony\Component\HttpKernel\HttpKernel->handle in /home/cctest/app/bootstrap.php.cache line 2918 at Symfony\Component\HttpKernel\DependencyInjection\ContainerAwareHttpKernel->handle in /home/cctest/app/bootstrap.php.cache line 2220 at Symfony\Component\HttpKernel\Kernel->handle in /home/cctest/web/app.php line 19at n/a in /home/cctest/vendor/doctrine/dbal/lib/Doctrine/DBAL/DBALException.php line 91 at Doctrine\DBAL\DBALException::driverExceptionDuringQuery in /home/cctest/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php line 701 at Doctrine\DBAL\Connection->executeQuery in /home/cctest/vendor/doctrine/orm/lib/Doctrine/ORM/Persisters/BasicEntityPersister.php line 748 at Doctrine\ORM\Persisters\BasicEntityPersister->load in /home/cctest/vendor/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php line 196 at Doctrine\ORM\EntityRepository->findOneBy in /home/cctest/vendor/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php line 241 at Doctrine\ORM\EntityRepository->__call in /home/cctest/vendor/claroline/core-bundle/Claroline/CoreBundle/Manager/ResourceManager.php line 1026 at Icap\BlogBundle\Repository\BlogRepository->findOneByResourceNode in /home/cctest/vendor/claroline/core-bundle/Claroline/CoreBundle/Manager/ResourceManager.php line 1026 at Claroline\CoreBundle\Manager\ResourceManager->getResourceFromNode in /home/cctest/vendor/claroline/core-bundle/Claroline/CoreBundle/Controller/ResourceController.php line 168 at Claroline\CoreBundle\Controller\ResourceController->openAction in line at call_user_func_array in /home/cctest/app/bootstrap.php.cache line 2815 at Symfony\Component\HttpKernel\HttpKernel->handleRaw in /home/cctest/app/bootstrap.php.cache line 2789 at Symfony\Component\HttpKernel\HttpKernel->handle in /home/cctest/app/bootstrap.php.cache line 2918 at Symfony\Component\HttpKernel\DependencyInjection\ContainerAwareHttpKernel->handle in /home/cctest/app/bootstrap.php.cache line 2220 at Symfony\Component\HttpKernel\Kernel->handle in /home/cctest/web/app.php line 19

If you configure the blog in a way that the owner should validate the article. If you give access to someone to add new article in your blog you have to validate the entry before the article is publish. After that the owner of the article can change the text without any validation.
The correct way should be : after a change in the text of an article the owner of the blog should have to validate the article before the article is published