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

base.py:323-325: Move content-based settings to db.... #518

Open
0pdd opened this issue Aug 15, 2018 · 1 comment
Open

base.py:323-325: Move content-based settings to db.... #518

0pdd opened this issue Aug 15, 2018 · 1 comment
Labels
1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time 3 we can defer this issue. But it'll good to implement it

Comments

@0pdd
Copy link
Collaborator

0pdd commented Aug 15, 2018

The puzzle 265-6e9b5ba6 from #265 has to be resolved:

# @todo #265:60m Move content-based settings to db.
# Content guys should be able to change settings like
# `MAIN_PAGE_TILE` or `FOOTER_LINKS` from admin panel.

The puzzle was created by duker33 on 15-Aug-18.

Estimate: 60 minutes,

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd
Copy link
Collaborator Author

0pdd commented Aug 15, 2018

@artemiyds2 @duker33 please pay attention to this new issue.

0pdd referenced this issue Aug 15, 2018
* #265  Move config.category_sorting_options to settings

* #265  Move config.cached_time to urls

* #265  Move last content-based options from config.py to settings.py

* #265  Ignore lint code duplication error

* #265  Review#1. Few naming fixes
@0pdd 0pdd mentioned this issue Aug 15, 2018
@duker33 duker33 added 1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time take it any teammate can take this issue and start working with it labels Aug 16, 2018
@duker33 duker33 added 3 we can defer this issue. But it'll good to implement it and removed take it any teammate can take this issue and start working with it labels Nov 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time 3 we can defer this issue. But it'll good to implement it
Projects
None yet
Development

No branches or pull requests

2 participants