Skip to content
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

feature request: add config names #7

Closed
arosenhagen opened this issue Mar 27, 2013 · 6 comments
Closed

feature request: add config names #7

arosenhagen opened this issue Mar 27, 2013 · 6 comments

Comments

@arosenhagen
Copy link

I love this extension very much especially when dealing with lots of (different) storeviews/websites.
As a bonus it'll be great to generally see the config names (eg. "dev/log/active") beside the fields in the magento backend interface. We heavily use n98-magerun to set those values automatically on deployment and it'll be a time saver if we could keep track of manual changes.

@amenk
Copy link
Collaborator

amenk commented Mar 27, 2013

+1

another interesting approach for the config deploying is with the firegento-contentsync module: magento-hackathon/firegento-contentsync#5

@arosenhagen
Copy link
Author

Thanks for referring (wasn't aware of that). Seems as if this could be exactly what I am looking for ;-)

@amenk
Copy link
Collaborator

amenk commented Mar 27, 2013

@arosenhagen But be aware that this feature is not yet implemented - would be great if you could implement it :-)

@avstudnitz
Copy link
Owner

I like the idea of the config names, will try to implement that soon (unless one of you does before).
The content sync module has some good concepts, but unfortunately it is not stable yet (I am one of the developers), we'd need some time to stabilize it. And the config deployment is an important feature for it, which is planned, but not yet implemented.

@arosenhagen
Copy link
Author

actually I don't know how the contentsync module works/is planned to work (as there's no documentation yet). Ideally this can replace manual lookup/sync of configuration changes, but in the meantime it'll be of great value to just see the config names so we can keep track of changes manually (e.g. in a ticketsystem). The current state is, that we have to dig into the database to get the proper name when documenting a change of a value...

@amenk unfortunately I'm not so keen on developing magento extensions, otherwise I would have picked up the hat ;-)

@arosenhagen
Copy link
Author

amazing... already integrated and love it from the start. thanks very much!!!

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

No branches or pull requests

3 participants