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

Enable to create new categorie on 2.0.2 #3833

Closed
PierreNau opened this Issue Oct 24, 2017 · 14 comments

Comments

Projects
None yet
3 participants
@PierreNau
Copy link

PierreNau commented Oct 24, 2017

Hi!
While creating a new categorie I get the following message:
500: Internal Server Error
I thought this issue sorted out?
Many thanks for your help!

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 24, 2017

Hi,

can you please check your browser's console to see whether an error is shown there?

@PierreNau

This comment has been minimized.

Copy link

PierreNau commented Oct 24, 2017

Below what I got from the console
Failed to load resource: the server responded with a status of 500 (Internal Server Error) contextMenu/edit/33

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 24, 2017

Is it possible that this problem occurs only for nodes containing children? Please check whether it works for leaf nodes (without any children).

@PierreNau

This comment has been minimized.

Copy link

PierreNau commented Oct 24, 2017

The problem occurs for leaf nodes as well ...
I experienced the same while trying to change the name with an existind category.
The only thing working is drag & drop a category from a folder to an other one while having the same message 500 (Internal Server Error)

@Guite Guite added this to the 1.5.3 milestone Oct 24, 2017

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 24, 2017

I just tried to reproduce this and got an idea: do you have additional core locales in your system (app/Resources/translations/)? If yes please try to rename this directory and see if it works then.

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 24, 2017

This problem is related to determination of locale names. Further investigating...

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 24, 2017

@PierreNau I think I fixed the problem. Can you confirm that it works with the patch shown in #3834 ?

@PierreNau

This comment has been minimized.

Copy link

PierreNau commented Oct 24, 2017

Thank you Guite for your help and investigation.
However, the problem is not fixed with the patch.
Moreover, I did not add additional core languages yet (French in my case)

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 24, 2017

Can you explain in detail how to reproduce the 500 error after applying the patch? Does it occur when opening the edit modal window or after submitting the form?

@paustian

This comment has been minimized.

Copy link
Contributor

paustian commented Oct 24, 2017

The bug is still there in Core 2.0.2. To reproduce the error do a fresh install of Zikula 2.0.2. When finished go to the Categories module and try to create a new category, it can be anywhere. When you hit submit you get a 500 error. This is what is shown in the javascript console

jquery.js:8630 POST http://localhost:8888/zikula_2_0/categories/admin/category/contextMenu 500 (Internal Server Error)   | send | @ | jquery.js:8630 -- | -- | -- | --   | ajax | @ | jquery.js:8166   | (anonymous) | @ | ZikulaCategoriesModu…ategory.List.js:232   | dispatch | @ | jquery.js:4435   | elemData.handle | @ | jquery.js:4121
If you look at ZikulaCategoriesModule.Category.List.js this is the code around line 232
$.ajax({ type: 'POST', url: Routing.generate('zikulacategoriesmodule_node_contextmenu', {action: data.action, id: entityId}), data: pars }).success(function(result) {
Could it be the route is just bad?

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 25, 2017

Thanks @paustian I am going to extend #3834 to fix this today.

@PierreNau

This comment has been minimized.

Copy link

PierreNau commented Oct 25, 2017

Hi Guite,
Nothing to add to Paustian's message. He described exactly what I experienced.
I did a fresh install as well with no improvement.
Thank you for your help.

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 25, 2017

First I could not reproduce this using 1.5.3-git with the patch from #3834.
Thus I will now merge #3834 into 1.5, 2.0 and master branches and continue testing using 2.0.3-git afterwards.

Guite added a commit that referenced this issue Oct 25, 2017

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Oct 25, 2017

fixed in db96a43

@Guite Guite closed this Oct 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment