I am wondering if we can have multiple sites connected to same composite C1 CMS? We are planning to create a mobile version of our site so the best bet would be if we can control the content of both sites through "One Common CMS" system.
I am thinking about folder structure like:
"Project Folder"(level1) -->> "WebSite(Composite C1) folder" (level2)
-->>"MobileSite (Composite C1) folder" (level2)
i.e mobile site is at same level as of main site
But that way those will be 2 separate installations both pointing to same database but i am concerned about state information and other details those composite store while saving content back to the database.
So the second structure could be :
"Project Folder" (level 1) -->> "WebSite(Composite C1) folder" (level 2) ->>"MobileSite (Composite C1) folder" (level3)
i.e mobile site as sub folder of main site.
Any help would be greatly appreciated
In Composite C1, you can create more than one website. Each website has its own homepage (the root page of the website).
In 2.1.1 version you have ability to associate different host names with different websites in C1 (on the Content perspective, right-click a home page (the root page of a website) -> click Manage host name.)
In 2.1.3+ version you can run multiple sites by using new ->Configuring hostname bindings.
Related
In my local instance of AEM 6.4, i'm not able to see 'page' option under create menu in sites.
i have created an editable template and enabled it.
what am i missing here ?
I have verified in Vanilla instance also, i don't see this option.
You ll need to create the root page for your site and add the property cq:allowedTemplates. Only then create page shows for the permitted templates.
You have to first create the project structure using the archetype project like maven archetype 13, refer this link for archetype 13, https://helpx.adobe.com/experience-manager/using/maven_arch13.html
This archetype also creates the basic content of a website with root page (example in this case: AEMTraining) and few language pages. Once you have created the project structure and your own global page is available under sites, click on the rootpage. Now, you can see the Page option under create, so you can use your editable template to create
your own pages. (Check the image)
Many visitors visiting our website by a link to content in a different language from their mother tongue. If they click on the language switcher, they will be redirected to the home link of the current menu. That means they have to navigate to the content again.
Is there a Plugin available that solve this problem?
The use should change the language and see the english version of the specific content.
That should not be the case, if you have set up bi/multi language in the right way.
Have you associated the articles to each others as well as the menu entrys?
You need to have exact copies of your menu.
Are you talking about "Content Pages" that have no menu entry? If so, try to create a menu which is not visible for the user, but use it to associate content.
You find the Association Tab in the Menu Entry Edit
The Falang component allows you to manage all your content translations, even the content of all your components/modules, on your web site.
Falang doesn't use the default language system of Joomla 2.5 and 3.3. You don't have to specify a language for each content article or menu item (which results in a huge amount of duplication). You don't need to create few menu copies, few articles/categories copies for different languages.
Here is described how to use it
I have just started learning DNN. I dug a little into this but I just can't change the layout for whole site. I am using Awesome cycle template as starting.
I need to redesign site header and footer. If I made change in Skins\Gravity\Home.ascx then these changes are only appearing to my home file.
I can change the CSS the way I want but I am just unable to change the base html of header in entire site. (like we do in master pages in ASP.NET or layout in MVC)
Your problem probably has to do with DNN supporting different skins for different pages.
You have to check if all pages use the same skin. I think that in DNN7 default site template pages use different skins. You can check this if you go to Edit Page -> Page Appearance -> Page skin
If you set all the pages to use the Gravity skin, then changes you make at the .ascx file will apply to all pages.
A uniform way to change the layout for the whole site is to set every page skin to 'None specified' and then only select skins from Admin -> Site Settings -> Basic Settings ->Appearance ->site skin.
You can update the DNN database using an update query on the Tabs table:
update Tabs set SkinSrc = REPLACE(SkinSrc,'OldSkinName','NewSkinName')
where SkinSrc like '%OldSkinName%'
You can also rename the containers using a similar query:
update TabModules set ContainerSrc = '[G]Containers/MySkin/NewContainer.ascx'
where ContainerSrc = '[G]Containers/MySkin/OldContainer.ascx'
In the latest operation remember to clean the dnn cache using : Host > Host Settings > Advanced Settings > Performance Settings , click on the “Clear cache” button.
I am using google analytics event tracking to track 2 Facebook canvas application. (they are similar just that one is for production and another is for development). Since they are 2 separate canvas application, both have a different canvas url.
Below is how I setup google analytics:
Property Name : Sample
Main profile (production)
Test profile (development)
Both profiles have the same Tracking ID. How can I track them separately? Do I need to create filters? I am not sure but I might be setting this up wrongly. Do I need to create a separate property name instead?
Appreciate any advice.
Yes, you need to create two separate filters. One that includes pages from your production domain or url, and one for your development domain or url.
Go to
Admin > [all accounts if you have more than one account linked to your GA account] > accounts > [click on specified account] > Filters > New Filter
Filter 1: (development)
Name your filter something descriptive like "production".
If the (sub)domains for your dev vs. prod are different, from the radio buttons/dropdowns, pick
predefined > include only > that are equal to > "dev.yoursite.com" or whatever your dev (sub)domain is.
If the (sub)domains for dev vs prod are the same (but different directory path, pick
predefined > include only > traffic to the subdirectories > that starts with > "path/to/dev/"
highlight the dev profile and click the add button to bring it over to the selected profiles. Click "Save" and you are done with the "development" filter. Now wash rinse and repeat but for your production profile.
With this setup, only data specific to the (sub)domain or directory path will go to your profiles. NOTE: This is not retroactive, any data GA received before you created the filters (even if the data is still in queue and hasn't actually shown up in reports yet) will still show up in your profiles.
You may be better off creating a new Google Analytics tracking ID to separate live production and your dev.
Simply go into GAnalytics Admin, create a new property underneath your already existing Account. Now you will have a new Tracking ID, it should be similar to your original tracking ID, except the last -X digit has incremented.
Now you can track Dev Vs Production in separate properties. We found this very useful when thousands of production users flood the data. Also good when running load tests with thousands of users on Dev, so it doesn't skew your production metrics.
cheers!
z
The Scenario
I have a website with several autogenerated menus:
Main menu ("root level" pages)
Tree menu (full tree down to current page)
Breadcrumb (only .ACT)
Now I see two possibilities regarding these menus and the RealURL extension.
Strategy A: Root as Front Page
I will create the page tree like so:
⊛ www.site.tld
↳ Page 1
↳ Page 2
↳ Page 3
Pros & Cons
Con: I will have to manually add a link to the "Front Page" (content from page "www.site.tld") to all permutations of the menus (as this is not on the same physical level as the other "root level" pages)
Pro: RealURL will per default render all links to the front page (the root page) as /
Strategy B: Front Page as Separate Page in Tree
I will create the page tree like so:
⊛ www.site.tld
↳ Front page
↳ Page 1
↳ Page 2
↳ Page 3
Pros & Cons
Pro: A link to the "Front Page" is automatically added to all permutations of the menus (as this is an explicit page on the correct level)
Con: RealURL will per default render all links to the front page as /front-page/ while I want it to link as /
Best Practice?
Is there a best practice in the front-page-as-root vs. front-page-as-separate-page question? I.e, should I go with A and manually extend the menus, or with B (if so, how to configure RealURL to render the correct links)?
Edit: The Answer
Phil provided me with a solution to the specific problem. Go with strategy B, but let the page "Front page" be a link (dokType = shortcut) to the root (the page "www.site.tld"). This will fix the menus and the links. ("Front page" being a shortcut, contents will reside on "www.site.tld".)
If anyone knows of alternatives to this one, please let me know. I do believe, however, that this will satisfy my needs concerning this issue.
I see 2 solutions (if I really understand youre question).
Put the Front page type to link, and link it to /
If you have access to the .htaccess, redirect /front-page/ to /
The solution B is easier, and it can be done without a special RealURL config