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

Hook problems while configure #3866

Closed
rallek opened this Issue Dec 2, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@rallek
Copy link
Contributor

rallek commented Dec 2, 2017

Q A
Zikula Version 1.5.3
PHP Version 5.6

Expected behavior

Hooks should be configurable always

Actual behavior

Problem one

e.g. in Scribite you may want to click on hooks to configure the hook system. But this is leading to an error message:
grafik

Problem two

all other modules where clicking on hooks do not bring this error you can not drop a new hook to the module.

Steps to reproduce

Problem one

go to scribite backend and click on hooks. I do have another simple fresh generated MOST module with the same behavior. Therfor I post it at the core.

Problem two

If you drop a hook to the module the frame is sticking somewhere but it is not creating the hook. After dropping it is not movable anymore. Normally the frame is flipping back to its position and the hook is registered. But that do not work.

@Guite Guite self-assigned this Dec 3, 2017

@Guite Guite added the Bug label Dec 3, 2017

@Guite Guite added this to the 1.5.4 milestone Dec 3, 2017

Guite added a commit that referenced this issue Dec 3, 2017

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Dec 3, 2017

fixed in 04c7321

@Guite Guite closed this Dec 3, 2017

@rallek

This comment has been minimized.

Copy link
Contributor

rallek commented Dec 3, 2017

Not everything is solved. For probhlem two I do have now the output from the web developer console:
Error: The route "zikula_hook_hook_togglesubscribeareastatus" does not exist.

@Guite

This comment has been minimized.

Copy link
Member

Guite commented Dec 3, 2017

Did you try deleting web/js/ ?

@rallek

This comment has been minimized.

Copy link
Contributor

rallek commented Dec 3, 2017

of course not :-/
That was it.

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