×
Please submit new Bug Reports on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues
Front-end state editing
Francesco
Nieuw lid
Posts: 1
9 jaren 7 maanden geleden #732
door Francesco
Front-end state editing werd gestart door Francesco
Hi,
I created a component with state frontend editing only, but when I try to edit item state sistem return attachment error page.
Specifically list view name is "codes" not "code" but component creator compiler generates below URL like attachment file explains:
<SEF component view alias name>/code/publish/<record ID>?state=0
I don't know if this is right, ask you. Anyway also changing "code" with "codes" nothing is updated
Tank you in advace and Regards
Francesco
I created a component with state frontend editing only, but when I try to edit item state sistem return attachment error page.
Specifically list view name is "codes" not "code" but component creator compiler generates below URL like attachment file explains:
<SEF component view alias name>/code/publish/<record ID>?state=0
I don't know if this is right, ask you. Anyway also changing "code" with "codes" nothing is updated
Tank you in advace and Regards
Francesco
Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.
David Villena
Moderator
Posts: 6
9 jaren 7 maanden geleden #735
door David Villena
Beantwoord door David Villena in topic Front-end state editing
Hi Francesco,
The wrong behaviour should be fixed by now.
The "code" controller, necessary to publish/unpublish an item, wasn't being included. Now it is, so you just have to re-build your component and re-install it (without uninstalling the previous version, so you don't lose your data).
And just a tip: if eventually you have a problem that seems to be caused by a bug on Component Creator, please use our contact form, so we can trace your request and answer it in a more efficient way.
Best regards,
David.
The wrong behaviour should be fixed by now.
The "code" controller, necessary to publish/unpublish an item, wasn't being included. Now it is, so you just have to re-build your component and re-install it (without uninstalling the previous version, so you don't lose your data).
And just a tip: if eventually you have a problem that seems to be caused by a bug on Component Creator, please use our contact form, so we can trace your request and answer it in a more efficient way.
Best regards,
David.
Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.
Tijd voor maken pagina: 0.068 seconden