Jahia CMS:
We are keeping default pages in the template, and these pages are created when we create a website using the template.
Now go to edit mode of the site, and delete a page from the site, and publish it.
Change something in template and deploy the new template again.
You will see the deleted page has reappeared for the edit mode, not for the published mode. Published mode is untouched.
Is it an expected behavior?
Yes it is the expected behavior.
What you mention as published mode is called "live mode". Creation of content has to be published before being available in live mode.
Only change made in templates does not have to be published.
Related
How do I edit the design (html, img, css) of the page hosted at [myapp].app.link? I have configured this in my Branch account configuration as the "Link Domain" for my app redirect.
This Branch.io help page seems to imply that the page is customizable: https://branch.io/what-is-applink/
As per Branch support: The page being referred to is called a Deepview. A Deepview is a mobile web splash page, hosted by Branch, that gives a preview of the in-app content behind a given Branch link.
For more information on the same, you can go through the documentation below:
https://help.branch.io/using-branch/docs/deepviews#overview
You can navigate to your Deepview setting from the Configuration page and then navigate to the Deepviews tab. You can not edit the existing Deepviews, however, you can create your own custom Deepview. Do go through the following documentation for a step by step guide:
https://help.branch.io/using-branch/docs/deepviews#1-enable-default-deepviews-templates
https://help.branch.io/using-branch/docs/deepviews#1a-create-a-custom-deepview-template
I'm running a portal based on Backbase and I have recently added a new LINK file (let's call it myLastLinkPath) in the following path:
src/main/import-scripts/portal/myPortal/links
The problem now is that when I access (through the browser) to my site, it redirects automatically to the last added link.
I mean, if I go to www.mysyte.com, it is redirectected to www.mysite.com/myLastLinkPath
It is the Default Landing Page of your portal.
You can check this in the portal configuration page, in the special pages tab
I am reading thru AEM WCM and had a question that once after creating page in lower environments and publish where to check that look and feel? Is there any url to check? or will check in AEM only?
can anyone give example format url?
TKs
Have a look at the Adobe Authroing documentation, understand the concept and architecture of the AEM. As AEM is on the REST based concept implementation your page content path will be the page url (if you don't have any sling internal redirects or Dispatcher level url hiding implementations).
Just to explain you taking an geometrixx website OOTB example.
Working at author end in local instance at port 4502:
Example if you have created a test page under /content/geometrixx/en/toolbar/
the test page url will be http://localhost:4502/cf#/content/geometrixx/en/toolbar/testpage.html
preview mode can be tested appending wcmmode=disabled at the end of your url as shown below
http://localhost:4502/cf#/content/geometrixx/en/toolbar/testpage.html?wcmmode=disabled
from side kick preview option
If you have published the page (assuming your publish instance is
running at 4503 on local)
your page path will be http://localhost:4503/content/geometrixx/en/toolbar/testpage.html
If you are using touch UI then you can see the preview mode by:
Edit link: http://localhost:4502/editor.html/content/geometrixx/en/toolbar/testpage.html
Preview Link:
http://localhost:4502/content/geometrixx/en/toolbar/testpage.html?wcmmode=disabled
You should have a Replication Agent and configuration setup there to publish the pages. There is a default agent comes with AEM where you can publish the changes from author to publish environment.
My jekyll blog is running ok in my pc but when I open it from my gh repository it's broken. Here's a screen of that
If I click on one of the links, that next page throws 404. Needless to say, I followed the steps from the gh site in order to configure it properly.
baseurl is set, the paths to css and images are correctly set using {{ site.baseurl }}. So locally the blog works fine, but still, on gh-pages it's not.
Code is here
Another piece of information. I have a master branch and a gh-pages branch, the one updated is gh-pages, master has old code, is it ok?
Any ideas please?
It works ! What you saw was an old version of your site.
Two possible explanations :
as #goyllo says : browser cache f5 or Ctrl+r can help.
Github pages is serving the old version and the new site generation is still pending.
In order to know if you last commit has been published it to go to https://github.com/goblind/modestoRimba/settings and to watch under GitHub Pages box.
If you see Your site is ready to be published at http://goblind.github.io/modestoRimba, your site generation is pending.
If you see Your site is published at http://goblind.github.io/modestoRimba, your site have been published with last commit.
It's working fine in my browser. I want to say one thing, GitHub pages cache your old resources(including HTML, CSS, JS, Images), in browser for better UX, For example, just disconnect your internet, and reload that page again, and it will be work fine, similarly if you visit another page, then it will not load your CSS, or javascript again from your website, they will load directly from browser cache. So you are getting this error because your browser use old cache resource, and it will update again in few hour, depending on cache time.
I want to say, if your blog working fine in localhost, then don't worry, it will be also work fine in github pages as well, otherwise github will send you notice in your email regarding page build fail.
in your _config.yml baseurl: /modestorimba R should be uppercase.
We have moved our codebase and wiki to github. However the google code version still shows up really high on Google. Is there any way to do an auto redirect to github when people land on the Google code version?
I'm not sure how long this option has been available (it may be related to Google announcing they're shutting down Google Code), but you can now set a "project moved" flag which will provide all visitors to your Google Code project with a link to any other site, including GitHub.
Note: It doesn't appear that you can fully revert this setting, at least not at the time of my writing this, so be sure you really don't want to access anything from the Google Code project before setting it.
You can mark your project as moved on your admin page. If you change your mind, you can clear the setting by clicking the publish button.
Setting the "Project Moved" Flag
Once a project has been successfully exported to GitHub, you will want to update your project's homepage on Google Code to avoid confusion.
Some project owners simply update their project homepage's text to indicate it has moved to GitHub. For example subtext or bwapi.
Another option is to set the Google Code "project moved" flag. When set, attempts to access the project will take users to an interstitial page indicating the new project location. In the future, the page will automatically redirect to well-known project hosting services such as github.com.
To set the "project moved" flag, navigate to your project's advanced admin page, at https://code.google.com/p//adminAdvanced.
Once there, enter the new project home page URL under "project moved". For example: https://github.com/google/kythe. Finally click the "Project Moved" button.
If you need to "un-move" a project, you can go back to the /adminAdvanced page at a later time and click "Publish". This will restore your project to its original state, before the move.