Closed darbula closed 11 years ago
I'd like to do something with some of these ideas, but I will need to discuss it first. One issue is that it is important that it should be easy to provide Entities with connections to other kinds of information through other applications.
For example, our Publications application makes it possible to see an Entity's academic research publications, and I am not sure how that will be affected by these changes.
There should not be any consequences to external applications but if you can provide some more details about certain parts that could become problematic we can discuss it.
I'm taking a good look at this now. There are some changes in the develop branch since you made this pull request, so I will reconcile those first, and make some a reminder to myself below about things that need tests and/or comments to explain their behaviour.
Person.get_absolute_url()
- test for self.active
get_absolute_url()
methods where not presentHave a look at https://github.com/evildmp/Arkestra/tree/merge-darbula-issue69. This:
I will do some more testing, and if this looks OK it's ready to be merged.
Merged in #106 - thanks.
Great, glad that this has worked its way into upstream :)
This pull request replaces pull/issue #69 as that issue seems to have some work ahead and by my mistake it did not have a dedicated named branch. Now I have made a dedicated branch
issue69
to be used to fix everything concerning following problem:Description:
Urls for contacts, news and vacancies were defined in multiple places:
urls.py
,models.py
- inurl_path
andmenus.py
- inurl_attribute
.This situation prevents changing/translating the default urls (i.e. contacts/ news/ etc). In this commit url patterns in
urls.py
are given names and thenreverse
is used to resolve urls where needed i.e. inEntity.get_related_info_page_url
or inURLModelMixin.get_absolute_url
.Url patterns are named so that their name can be deduced from
url_path
andurl_attribute
when needed.