Jekyll Blog Contact Page Permalink not Working - url

I have my Jekyll blog set up here: My blog
I forked this blog theme from https://github.com/johnotander/pixyll
and created a github pages for it using the Master branch and changed the name of the repository to 'blog'.
My github.io repo is used for my personal site and uses the CNAME: edsonmendieta.com
So, my blog is at edsonmendieta.com/blog.
In my _config.yml: https://github.com/edsonmendieta/blog/blob/master/_config.yml
I've set the url to: 'http://edsonmendieta.com/blog/'
My blog theme, has a contact page which had 'permalink' set to /contact/,
but after clicking it, the url path was edsonmendieta.com/contact, and I got a github 404.
I changed the permalink to blog/contact/ and now I still get a 404 but one that's themed by my blog theme.
I don't know why I'm getting a 404.
The 'baseurl' in my config.yml file is empty ("").
Should I change the 'baseurl' and 'url' in the _config.yml file?
Should I change the 'permalink' in the contact file?
Help is GREATLY appreciated, thank you.

In config, set :
url: http://edsonmendieta.com
baseurl: /blog
And it's supposed to work out of the box.

Just change the permalink on the contact page and it should work. You can even remove it, jekyll will take care of it for you.

Related

Netlify CMS - blog posts from BitBucket show on front end but not back end CMS

I am having a problem using Netlify CMS with BitBucket.When I create a post in the CMS editor it saves correctly to the BitBucket repo,Netlify does a build and it publishes to Gatsby front-end without any problem.
However,when CMS is refreshed,none of the posts are visible,so cannot be edited without going into BitBucket and editing directly or pulling to local repo for editing and pushing again.Obviously this defeats the purpose of a CMS in the first place.
For reference I am using the Kaldi Gatsby/Netlify CMS starter the source code for which can be found here.
Here is what I see in the CMS directly after a post is created.
But when the CMS page is refreshed the Blog list is empty despite the post saving to BitBucket and showing on front-end.
I have looked through the Gatsby code trying to find something which could be causing the posts not to display in the CMS,but cannot see anything.If anyone has any ideas where to look or why this is happening I'd be grateful for any help.Thanks in advance!
UPDATE
Incidentally,the web pages included in the Kaldi template show up fine in the CMS.
I checked the console after trying to load the blog collection and it lists the error below for all the post markdown files.So it seems the CMS is trying to get them but can't for some reason.Unfortunately,the expanded view of the error doesn't offer any pointers to the source of the problem.
Thanks again for any assistance!

Links issue when I deploy my Hugo site as a Github Pages project

I created a Hugo site that working well locally. I deployed my Hugo site as a Github Pages project via a /docs folder on the master branch.
So now, I have my Github Page project and my URL looks like that:
https://myname.github.io/myrepository/myHugoSite.
I have a problem with my link. All my links redirect to https://myname.github.io/ but not https://myname.github.io/myrepository/ because my links are /next-page/. These links are working locally because I don't have a repository.
My question is: Do I have to add /myrepository/ to all my links or there is another solution?
You need to add your site prefix to the baseUrl parameter in the config file. In your case the prefix is myrepository/
If you are using TOML format in your config file it would look like this:
baseUrl = "https://myname.github.io/myrepository/"
Note that with Higo 0.62.1 (and more recent), you can have portable links.
See bep/portable-hugo-links as an example.
truly portable Markdown links and images. No shortcodes used.
This page includes the following links, which would be rendered correctly both on GitHub and Hugi generated pages:
* [Blog Link1](../blog/p1/index.md)
* [Blog Link2](../blog/p2.md)
* [Home Page](/README.md)
* [Local Anchor](#et-illis-ossaque-loqui-ille)

gh-pages, Landing page

Can we set a Landing page by a name other than index.html or a different path . I tried and it dint work. Searched and din't get any relevant solution, I am not using Jekyll or other template engine.
On github Pages the default page served on domain.tld/ or domain.tld/any/path/ is index.html.
There's not setup available to change that.

Umbraco URL without domain prefix for the multisite setup

We have mutli site setup with "UseDomainPrefixes" set to true and have applied the hostname on the root level of each site but what is required is "Link to Document" to should be the url with-out the domain/hostname prefix. I was able to achieve this in umbraco4.0.2 but we recently upgrade to 4.8.0 and this upgrade has replaced all the links with domain prefix. Is there any way to achieve tihs in 4.8.0.
Site setup and url of a page in umbraco 4.0.2
Hence the link to document doesn't have the domain prefix set on it only for the first site even though "UseDomainPrefixes" set to true. i need to replicate exactly the same thing in 4.8.0 due to the way the site has been setup.
The same page in umbraco4.8.0
Please Help, Much Appreciated.
Thanks
Aneesh

ModX: Changed to Friendly Alias URLS but now Wayfinder isnt working

I've used Wayfinder in my template, eg:
[[Wayfinder? &startId=`8` ]]
and it was working fine until I turned on friendly urls (by going: System>>System Settings>>User Friendly URLS)
Now none of my links work. On top of this if I click the 'View' button from a resource page or enter the full url into a browser I get a 404 error.
Am I missing something in this process?
(ps Im using Revo 2.1.3)
Have you configured your .htaccess file? It's required for friendly urls. When you install MODX it's named ht.access, so you'll need to rename it to .htaccess.
If you've installed MODX in a subfolder you'll also need to set it here:
RewriteBase /folder-name
As Sean suggested, you'll also need to clear your cache to have your Wayfinder menu rebuilt.
it's probably your cache - just clear it and you should be fine.

Resources