URL field does not show up in Admin when editing a link

[Christopher Vo]

I am using Mezzanine 3.1.10

The attached screen shot shows the problem. Notice how there is no "URL" field when I try to edit a link.
Is there any reason why this would happen?

[Christopher Vo]

I even went into the Mezzanine source code:

At mezzanine/pages/admin.py:224
Added the line "print fieldsets"

And verified that 'slug' appears among the fieldsets! But it still doesn't display on the admin....

[Josh Cartmell]

That's strange, it always shows for me.  Could there be some stray javascript that is hiding it?

Is it present in the page source?

--
You received this message because you are subscribed to the Google Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Christopher Vo]

Yes, in fact, you can see it in the page source.

Christopher Vo

--
You received this message because you are subscribed to a topic in the Google Groups "Mezzanine Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mezzanine-users/qKrpWVmrcgw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mezzanine-use...@googlegroups.com.

[Christopher Vo]

I found where it's happening in the source output:

<link rel="stylesheet" href="/static/mezzanine/css/admin/global.css">

<style>

    /* These are set in PageAdmin's view methods, and mezzanine.core.admin.SingletonAdmin */

    .slug {display:none !important;}

</style>

<script>

Christopher Vo

[Josh Cartmell]

I'm not sure why that's there.

It's not present on the dev site, mezzanine.jupo.org/admin

Could you try creating a completely vanilla project and see if it's still happening?

[Christopher Vo]

And here is where it's happening in the PageAdmin's view methods.

Apparently it hides the slug field if you have overridden it. 

I'm not sure why that would make sense.

kwargs["extra_context"].update({

    "hide_delete_link": not content_model.can_delete(request),

    "hide_slug_field": content_model.overridden(),

})

Christopher Vo

[Josh Cartmell]

I'm not sure why I didn't think of this before, but I think I understand what is happening now.  If the slug field matches a url somewhere in a urls.py Mezzanine hides it.  This is to prevent an admin user modifying it, not realizing the slug needs to match the url.

Does the url you set match an existing url?

[Christopher Vo]

Yes, this seems to be what is happening. It's linked to an existing url and so it's preventing its modification.

Now that I think of it, this is a desirable behavior on a production site.

Thanks for your help Josh. 

Christopher Vo

[Josh Cartmell]

No problem, I think someday it would be nice to update it so there was a setting somewhere that would toggle this behavior, that way if you really did know what you were doing and had accidentally set a slug that overlapped a URL you could fix it without having to mess with the database directly.

Good luck!

[Christopher Vo]

Or perhaps "greyed out" so you can't edit it but at least you know where the link points to. That was the main problem for me; the end user wanted to know what the link was pointing to but it wouldn't even show in the admin.

Christopher Vo

[Wim Feijen]

Hi all,

I ran into the same problem. I find it confusing that we sometimes hide the link, the more so when we have trouble explaining what happened.  

My proposal is to just show the url all the time, and point out that: "Things might break when you change this. Don't change it unless you know what you are doing." in the help_text.

In my case, the end user is smart and knows what he is doing. And urls were pointing at the live site in stead of the test site, while still remaining hidden so the end user could not solve it.

I would rather give a warning than create limitations.

Let me know if you find this desirable and I will make a pull request when I find time.

Wim