Hi Joel,
It looks like you have a custom header for your application that uses the
'user_can_edit' convention. This has been deprecated in the v3.1 and
requires some adjustments to custom headers (Alexei will be making a more
general post on this later today).
In the meantime, there are a few changes you can make to your header.htm
file to account for these changes. First, to change the login displaying
'Welcome Anonymous - Logout' you can replace the "Login/Logout" link in
your header.htm (approximately line 31) with the following:
<a id="auth-link" href="{% url 'auth' %}?next={{ request.get_full_path }}{%
if user.username != 'anonymous' %}&logout=true{% endif %}">{% if
user.username == 'anonymous' %}{% trans "Login" %}{% else %}{% trans
"Welcome" %} {{ user.username }} - {% trans "Logout" %}{% endif %}</a>
For access to the Resource Manager and the RDM you can replace your current
code from approximately lines 89-110 in header.htm with the following:
{% if 'edit' in user.user_groups %}
<!-- Resource Editor-->
<li class="dropdown {% if active_page =
'ResourceManger' %}active{% endif %}">
<a href="javascript:void(0);"
class="dropdown-toggle" data-toggle="dropdown">
{% trans "Resource Manager" %}
</a>
<ul class="dropdown-menu">
{% for type, type_data in resource_types %}
<li><a href="{% url 'resource_manager' type
type_data.default_page '' %}"><i
class="{{type_data.icon_class}}"></i>{{type_data.name}}</a></li>
{% endfor %}
</ul>
</li>
<!-- End Resource Editor -->
<!-- RDM-->
<li class="{% if active_page = 'RDM' %}active{% endif
%}">
<a href="{% url 'rdm' '' %}">
{% trans "RDM" %}
</a>
</li>
<!-- End RDM-->
{% endif %}
Hope this helps.
Ryan
On Friday, November 20, 2015 at 7:14:48 AM UTC-8, Adam Cox wrote:
>
> Hi Alexei and Joel, something very strange is going on now: anonymous
> users seem to have full write privileges without logging in. Here's
> <http://52.34.18.214/search?page=1&termFilter=%5B%7B%22inverted%22%3Afalse%2C%22type%22%3A%22term%22%2C%22context%22%3A%22ff603838-4017-11e5-bc29-efc5b8c809eb%22%2C%22context_label%22%3A%22Name.E41%22%2C%22id%22%3A%22Adam%20Created%20This%20Resourceff603838-4017-11e5-bc29-efc5b8c809eb%22%2C%22text%22%3A%22Adam%20Created%20This%20Resource%22%2C%22value%22%3A%22Adam%20Created%20This%20Resource%22%7D%5D&temporalFilter=%7B%22year_min_max%22%3A%5B%5D%2C%22filters%22%3A%5B%5D%2C%22inverted%22%3Afalse%7D&spatialFilter=%7B%22geometry%22%3A%7B%22type%22%3A%22%22%2C%22coordinates%22%3A%5B%5D%7D%2C%22buffer%22%3A%7B%22width%22%3A%220%22%2C%22unit%22%3A%22ft%22%7D%2C%22inverted%22%3Afalse%7D&mapExpanded=false&timeExpanded=false&include_ids=true>
>
> proof. It is the same for the production instance.
>
> Joel are you sure you are using arches 3.1.1?
>
> It looks like what's happening is a mix of arches-hip versions and arches
> versions. Now a user is authenticated as "anonymous", and in your
> installation the arches context_processors.py file doesn't seem to have
> been updated to handle this correctly...
>
> Adam
>
> On Fri, Nov 20, 2015 at 2:11 AM, Joel Aldor <[email protected]
> <javascript:>> wrote:
>
>> Hi Alexei,
>>
>> I was able to finally fix the website by updating our Apache
>> 000-default.conf file to reflect the WSGIDaemonProcess arches python-path=
>> /home/ubuntu/Projects/crip:/home/ubuntu/Projects/*ENV2*
>> /lib/python2.7/site-packages to point to the new ENV2 that I created,
>> which contains the update. Hence the reason why the website was not working
>> properly after the upgrade and patch, even though I did collectstatic twice.
>>
>> I think this should be noted on the documentation too, especially if
>> there were a lot of virtual environments set up and you're using Apache for
>> your production server.
>>
>> All good now. Will update our production server in a bit. Thanks a lot!
>>
>> Regards,
>>
>> Joel
>>
>> On Friday, November 20, 2015 at 3:32:35 PM UTC+8, Alexei Peters wrote:
>>>
>>> Hi Joel,
>>> I don't think collectstatic worked, because I can still see a reference
>>> to the old knockout.js version (it's currently supposed to be 3.3.0).
>>> You might try running collectstatic with the "-c" option which will
>>> clear the existing files first.
>>> Give that a shot.
>>> Cheers,
>>> Alexei
>>>
>>>
>>> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>>>
>>> On Thu, Nov 19, 2015 at 11:26 PM, Joel Aldor <[email protected]> wrote:
>>>
>>>> Hi Alexei,
>>>>
>>>> Did that collectstatic command too before this issue was posted.
>>>>
>>>> I'll check as well if I need to update my apache config file since I
>>>> switched to a separate virtual env when I upgraded to this version,
>>>> although I'm not sure if it has to do with the issue. What do you think?
>>>>
>>>> Joel
>>>>
>>>> --
>>>> -- To post, send email to [email protected]. To unsubscribe,
>>>> send email to [email protected]. For more information,
>>>> visit https://groups.google.com/d/forum/archesproject?hl=en
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Arches Project" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> -- To post, send email to [email protected] <javascript:>. To
>> unsubscribe, send email to [email protected] <javascript:>.
>> For more information, visit
>> https://groups.google.com/d/forum/archesproject?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Arches Project" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
-- To post, send email to [email protected]. To unsubscribe, send
email to [email protected]. For more information,
visit https://groups.google.com/d/forum/archesproject?hl=en
---
You received this message because you are subscribed to the Google Groups
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.