Development

New response in thread: External links in menu. Again.

lauri — Thu, 10 May 2012 17:23:45 GMT

Thanks for such a detailed reply.

Agree with external links to a different websites.

But one more use case for external links exist.
It very well might be that link must be pointing to another web application on same web server. Just like its done on magnolia's home site in example above in the thread.

Lauri.

New response in thread: External links in menu. Again.

lauri — Wed, 09 May 2012 13:04:26 GMT

Feature request: http://jira.magnolia-cms.com/browse/MAGNOLIA-4404 as Had has suggested.

New response in thread: External links in menu. Again.

runger — Wed, 09 May 2012 13:03:53 GMT

Hi Lauri,

We have discussed this Issue at length when designing our templates. We don't use STK, so we have complete freedom to build our templates the way we want.

We advised our customer to consider the following:

As a general useability rule, it is a bad Idea to mix different link-types in the same navigation. If you have a "typical" left-hand menu corresponding to your site-structure, then it will be "unexpected" for the user if some of those links open external sites in new windows, while others change the current page to a new page in the same site.
Therefore we advise our customers to stick to one navigation concept, and, for example, only offer internal links in the left-hand menu.
If you want to link to an external site, then perhaps it would be better to operate as follows:
- use teasers, for example in the right-side-bar
- provide an alternate navigation, perhaps at the top, or below the normal left-hand navigation, to hold the external links
- provide a "links" area as part of the content, where you list relevant links for the content, and can include external links

However, customers being as they are, they of course ignored our advice, and demanded the ability to include external links in the navigation.

We solve this in 2 ways, depending on the type of navigation:

1. For explicitly configured navigation-menus, we simply provide paragraphs for internal and external links, and allow the user to insert whatever link-type he or she wants into the menu.
2. For implicitly configured navigations, ie when the navigation automatically is created from the site-content, we provide a special page template. The editors can create an "externalLinkPage" and configure the link within the page properties for that page. The page has no other content. If accessed directly on the public instance, the page redirects to the parent page or the home-page. When rendered in the navigation menu, the page causes an external link to be rendered in the menu.

Regards from Vienna,

Richard

-----Ursprüngliche Nachricht-----
Von: dev-list-owner@magnolia-cms.com [mailto:dev-list-owner@magnolia-cms.com] Im Auftrag von Lauri (via Magnolia Forums)
Gesendet: Mittwoch, 09. Mai 2012 14:48
An: Magnolia Dev List
Betreff: [magnolia-dev] External links in menu. Again.

Hi.

A question to developers.
Why don't you anticipate external links in menu?

There is an old thread with long answer why an item in menu should not be seen as a link.
That's wierd to my opinion since it leads to strange navigation schemes like one you have on magnolia site:
http://www.magnolia-cms.com/community/forums.html
Note: forums link doesn't lead to forms like expected, instead its a huge blabla page with some inline link in the middle (Really, why should you explain what forums are?).

Easiest workaround should be a special template which would redirect user to external page defined.

Proper solution would be something which would render external link right in the menu. Smth like workaround mentioned above + replacement to cmsu:simpleNavigation tag and others. So those would be aware of template settings before rendering a link.

Do I get it right? How would you do it?

Lauri

New response in thread: External links in menu. Again.

lauri — Wed, 09 May 2012 12:58:15 GMT

Whoops, i've missed answer to my prev question . Sorry. By anyway, question remains valid, isn't it?

New thread: External links in menu. Again.

lauri — Wed, 09 May 2012 12:48:16 GMT

Hi.

A question to developers.
Why don't you anticipate external links in menu?

There is an old thread with long answer why an item in menu should not be seen as a link.
That's wierd to my opinion since it leads to strange navigation schemes like one you have on magnolia site:
http://www.magnolia-cms.com/community/forums.html
Note: forums link doesn't lead to forms like expected, instead its a huge blabla page with some inline link in the middle (Really, why should you explain what forums are?).

Easiest workaround should be a special template which would redirect user to external page defined.

Proper solution would be something which would render external link right in the menu. Smth like workaround mentioned above + replacement to cmsu:simpleNavigation tag and others. So those would be aware of template settings before rendering a link.

Do I get it right? How would you do it?

Lauri

New thread: Product Meeting (2012.05.07)

pbaerfuss — Mon, 07 May 2012 13:27:49 GMT

Hi,

In the future you find a summery of the protocols and other information related to our product development on our team blog.

--> http://dev.magnolia-cms.com/blog/2012/05/product-meeting-7-mai-2012

Enjoy!

- philipp

New thread: Parent POMs version 23 released

gjoseph — Mon, 30 Apr 2012 17:22:41 GMT

Hi there,

Just released version 23 of our parent poms, which should help working around Eclipse's oddities.

See BUILD-72 [1] for details.

Cheers,

-greg

[1] http://jira.magnolia-cms.com/browse/BUILD-72

New thread: Product Meeting (2012.04.30 )

pbaerfuss — Mon, 30 Apr 2012 09:39:31 GMT

Infrastructure
- Git Migration
-- we are ready, waiting for the 4.4.7 release

Community
- created a product blog: http://dev.magnolia-cms.com/blog/
- product related posts: roadmap/planning, protocols

Magnolia 5
- Architecture document: https://docs.google.com/document/d/13rqtHSlO9hp43ZMsjiGTPwViJBWbmlo3oERaz5lIdD8/edit
-- a lot more material (diagrams and questions)
-- you can comment

- Magnolia Shell, how to run multiple instances in the same browser?
-- PoC for using the window.name property

- HTML prototype
-- frames on iPads
-- gestures (swipe for app switching)
-- focusing on forms

Maintenance
- Performance tests
-- 4.5 is slower than 4.4 (20%)
-- Workshop, Wednesday, 14:00, analyze the results together
-- JMeter, scripts for testing
-- JProfiler, we got a free license

Magnolia 4.4.7
- to be released this Wednesday
- 5 reopened tickets

Magnolia 4.5.3
- tentatively mid of Mai
- priority is to migrate remaining modules (most done)
- will ship jackrabbit 2.4.1

New response in thread: Google sitemap for multiple site work around

fgrilli — Tue, 24 Apr 2012 10:36:24 GMT

Hi,

thanks a lot for providing this workaround. We are currently in the process of updating (to Magnolia 4.5) and refactoring the google site module http://jira.magnolia-cms.com/browse/MGNLGS-6 which should be released soon. We will apply your patch and test it before eventually making it into the final release.

Cheers,

Federico

New response in thread: Google sitemap for multiple site work around

kunal_mshah85 — Mon, 23 Apr 2012 21:42:44 GMT

so i have a complete work around for site map thing.
1) create a html page which has logic to read site map generated by magnolia tool which has "localhost" thing
2)do a string replace and write it to sitemap.xml file in docroot using same html page (i.eyou can have back and java servlet to do all this)and you can have robots.txt t same place
3)set up redirect rule and Content-Disposition rule for both xml and txt content.

so we can have sitemap file in xml format and in root directory (ideal but not required).