Issue 13911

Bad menu entry for Community-Networking

13911
Reporter: feedback bot
Assignee: mdoering
Type: Feedback
Summary: Bad menu entry for Community-Networking
Description: This leads to http://portaldev.gbif.org/networking/nlink1 which does not exist and shows the front page. Create under construction page instead like elsewhere
Resolution: Fixed
Status: Closed
Created: 2013-09-16 10:28:25.661
Updated: 2013-09-16 16:58:45.232
Resolved: 2013-09-16 16:58:45.181
        
    


Author: mdoering@gbif.org
Comment: The resulting page just seems to be the homepage, but the ajax metrics are not there and also the search leads to somewhere different, a non existing member search. How does this happen and how can this be avoided for all 404's?
Created: 2013-09-16 10:31:10.836
Updated: 2013-09-16 10:31:10.836


Author: cvizitiu@gbif.org
Created: 2013-09-16 11:17:35.189
Updated: 2013-09-16 11:17:35.189
        

Works via direct call to Drupal e.g. on staging:

http://staging.gbif.org/networking/nlink1

Probably a varnish issue. 
    


Author: mdoering@gbif.org
Comment: it has to be fixed, cant close it as wont fix. Lets see if its varnish
Created: 2013-09-16 12:32:35.963
Updated: 2013-09-16 12:32:35.963


Author: mdoering@gbif.org
Created: 2013-09-16 15:54:57.556
Updated: 2013-09-16 15:54:57.556
        
indeed it is a varnish "problem". We use the url /network already for java app pages, so varnish directs to java, not drupal.
It owuld be very, very good if we can avoid using drupal urls which start with any of the following prefixes:

{noformat}
dataset|occurrence|species|member|node|network|publisher|developer|country|cfg|css|fonts|img|js|favicon
{noformat}

Can this be done? Anything else leads into rewriting hell. Alternatively we *could* consider mounting all data java urls under /data/, e.g /data/dataset or /data/network but that has a huge impact we should carefully consider
    


Author: trobertson@gbif.org
Created: 2013-09-16 15:58:00.679
Updated: 2013-09-16 15:58:00.679
        
why not just add a trailing / to the prefix regex?  This is presumably caught because we have /network/ and the regex is catching networking in "network*".  If it were "network/*" it would not.

but otherwise, we do need to reserve those works from Drupal URLs
    


Author: mdoering@gbif.org
Comment: in this case it should work as do not have a /network homepage, but for /dataset we do. Ill apply the "fix" for network now, but it would really be good to avoid those names in the future
Created: 2013-09-16 16:01:09.082
Updated: 2013-09-16 16:01:09.082


Author: thirsch@gbif.org
Comment: Apologies but these are not in fact final titles for these tabs - I have been awaiting guidance from Alberto on what we should call the two pages but they are likely to be networking/summary and networking/communitysite . I will aim to make these changes and create pages with the relevant paths before next UAT deployment
Created: 2013-09-16 16:22:30.542
Updated: 2013-09-16 16:22:30.542


Author: mdoering@gbif.org
Comment: https://code.google.com/p/gbif-portal/source/detail?r=2096
Created: 2013-09-16 16:58:45.23
Updated: 2013-09-16 16:58:45.23