Skip to content
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.

[WIP] Handling of CreateJs on the CMF website #9

Open
wants to merge 58 commits into
base: master
Choose a base branch
from
Open

[WIP] Handling of CreateJs on the CMF website #9

wants to merge 58 commits into from

Conversation

adou600
Copy link
Member

@adou600 adou600 commented Oct 11, 2012

Those wanting to try out content creation, go to /login and use editor as the username and dummy as the password, then go to /news and click edit and scroll to the bottom. You will see an add button (actually currently 4 due to a bug) to add a new news item.

Until the feedback and merge of the other repositories, I will continue to work on the following:

  1. figure out how to deal with the existing content if saving from the news overview page
  2. figure out why there are two "add" buttons for collections
  3. fix the footer layout on the news overview page
  4. take the modification date into account when saving and create a new element or updating some
  5. use another sioc property than post to be able to differentiate the news and page, and then enable the CreateJs modification of the pages

This discussion can be helpful: openpsa/createphp#26

@lsmith77
Copy link
Member

before we can merge/deploy this we also need to add a simple login form. guess it can just use basic auth with a password set inside the parameters.yml. which also means we need to rename the parameters.yml and add an ignore on it.

my_memory_provider:
memory:
users:
editor: { password: dummy, roles: 'ROLE_EDITOR' }
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lsmith77 how can we handle the login and password for the site on production? I went for the memory providers since it's the easiest way to deal with user authentication. To login, you just need to go to the URL cmf.symfony.com/login. Don't hesitate to tell me if you see a better way to do it.

@adou600
Copy link
Member Author

adou600 commented Jan 4, 2013

@lsmith77 FMPOV, now we just need to decide what we do with the Create.js bugs listed at the end of #9 (comment). I think that when openpsa/createphp#29 and openpsa/createphp#44 will be closed some of the problems listed will disappear. The usability is not very good because of that, but it is still possible to add news... WDYT?

@lsmith77
Copy link
Member

lsmith77 commented Jan 4, 2013

i think we should push on .. we are not yet in a stable state .. to anything that moves us forward is good and will increase the chances of more people joining to help us fix the remaining issues.

@lsmith77
Copy link
Member

lsmith77 commented Jan 4, 2013

if @dbu does not have any objections i say we merge this!

@dbu
Copy link
Member

dbu commented Jan 9, 2013

yes i think it makes sense to merge. this has grown quite long.

does it depend on the createphp PR to be merged too?

the only worry i have is that if we actually start to use it, we also need to ensure we back up data and that we do not destroy data by reloading the fixtures. is this handled?

@adou600
Copy link
Member Author

adou600 commented Jan 10, 2013

@dbu it is not concerned by the last changes on createphp (openpsa/createphp#45) because it is only needed for the route creation on the Sandbox. But it has been closed anyway.

I can't do a lot about backups, but tell me if I can do something about the fixtures. There are still quite useful to debug and develop, but I indeed see the danger to keep it like this... Would a check during the fixture loading about the current environment be enough?

@lsmith77
Copy link
Member

we can probably talk to server grove about this as they host the CMF website. @pgodel ?

Adrien Nicolet [email protected] wrote:

@dbu it is not concerned by the last changes on createphp (openpsa/createphp#45) because it is only needed for the route creation on the Sandbox. But it has been closed anyway.

I can't do a lot about backups, but tell me if I can do something about the fixtures. There are still quite useful to debug and develop, but I indeed see the danger to keep it like this... Would a check during the fixture loading about the current environment be enough?


Reply to this email directly or view it on GitHub.

@ghost ghost assigned adou600 Jan 24, 2013
@@ -14,6 +14,11 @@
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
{% endblock %}
{% if is_granted('ROLE_EDITOR') %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean? I don't see how I can produce the same effect with IS_AUTHENTICATED_ANONYMOUSLY.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what I was trying to tell you is to configure the role via the config.yml so that you don't need to check it in the template

@adou600
Copy link
Member Author

adou600 commented Mar 9, 2013

After this commit I can't add news anymore. There is a weird issue with create.js when I click add.
create js-bug

I can't figure out what is happening. Any idea? Did we miss important changes in Create.js?

@dbu
Copy link
Member

dbu commented Mar 9, 2013

the create.js version is only controlled by the submodule that CreateBundle specifies. i suggest you try to manually use older versions of createjs using the git log and git checkout specific commit ids to see when it starts, and maybe the change indicates what goes wrong. if there are many commits, you could use git bisect between the version of createjs the version of createbundle before this update had.

@dbu
Copy link
Member

dbu commented Mar 18, 2013

hi @adou600 did you have any luck figuring out what the problem is, when it started or what could be done? if you want to pass by the office to have a look together, contact me on skype or irc, could take an hour today, tomorrow or wednesday. afterwards i am in holidays and staying in bern (where we could meet but its a bit far...)

@adou600
Copy link
Member Author

adou600 commented Mar 22, 2013

My bad, I didn't update the twig template used to display the news... There are now using the noautotag attribute and the creation of news with create.js is working fine again.

However, I had to manually rebase the jms/Serializer. I should use the version 0.12 but the CreateBundle allows 0.11.

@dbu
Copy link
Member

dbu commented Mar 22, 2013

great! if you are sure about CreateBundle and the serializer version, can you please create a pull request so we do not have wrong dependencies there?

are you working on the refactoring of createphp? oh, but that would not be needed for this feature as the website is single language. would this be ready to merge?

@adou600
Copy link
Member Author

adou600 commented Mar 22, 2013

I'm not sure about this serializer version... May be someone should try to checkout the project and see if it works on his machine as well. I think this is the only thing left to do for this PR.

@lsmith77
Copy link
Member

well i think composer is just having some issues with conflicts. CreateBundle does indeed work with 0.11 and 0.12 .. but FOSRestBundle does not. i guess the quick fix would be to just configure CreateBundle to require 0.12 .. but actually there is a bug in composer that is causing the issue.

see https://twitter.com/lsmith/status/315081682908753920 /cc @Seldaek

@dbu
Copy link
Member

dbu commented Apr 18, 2013

@lsmith77 you wanted to do something with the migrations tool. and think about the backup.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants