My problem is when I try to connect the HUGO theme with Netlify cms, using an official Netlify guide and also 1 blog on how to connect Hugo with netlify cms, when I try to open website/admin then I always get page not found. After adding java snippets in the partials footer.html file, now the cms page is opening but it shows a totally blank page without showing any errors.
Can you tell me what to change as i am new to this and its really confusing to configure netlify cms with ssg themes
I have added two files admin/index.html and admin/config.yml in static folder but still I am not able to authenticate netlify cms with my theme
Github repo i am using: https://github.com/h-enk/henkverlinde.com
AFAIK, your /static folder should contain an admin subfolder, in which a config file and an index page should be.
Related
I have a classic static Docusaurus site working fine.
I also generate a static Doxygen website.
When I open the Doxygen site only, the site is properly generated:
Now if I put the Doxygen website in the static/code folder of the Docusaurus project, the Doxygen files are properly moved at the root of my website after building Docusaurus project.
Now if I visit mywebsite.com/code I see the Doxygen website, but without any JS, and the logo isn't found, as you can see:
How do I integrate another static site into a Docusaurus site? I don't need the Docusaurus layout for this other site, I just want it to work as if it were at the root of the site, but in a sub-folder.
I am trying to resolve the "leverage browser caching" warning for my jekyll blog. I have consulted the HTML5 boilerplate github and cloned the project. I then copied over the .htaccess file into the root directory of my own blog, however, when I retest my website, I still have the same browser caching score. I have confirmed that there is language related to expiration dates within the .htaccess file. My github project can be found here:
https://github.com/thedatasleuth/thedatasleuth.github.io
.htaccess is for an Apache web server. Github pages is not an Apache web server and whatever server technology it is, they don't allow you to adjust those settings.
I'm trying to implement an email marketing email using a few widgets that gets triggers on submission of a form. Everything has been built and works locally but having issues with the CMS once uploaded to any hosted environment ('CI' and 'UAT' as we call them).
From what I can see everything has been sent up correctly but when editing templates there seem to be some CMS styling issues from some of the iframe loaded elements.
Have attached a screen grab as an example.
There are no console errors and no errors in the Kentico logs so I'm a bit stumped as to what is causing this issue.
Thanks in advance,
Luke
Solved this issue. We had recently upgraded from a previous version of Kentico and the associated updated stylesheets hadn't been uploaded to the development environments so were missing styles in these new areas of the CMS
I understand that .htaccess is not supported by GitHub Pages. Is there an alternative for password-protecting particular directories for websites hosted by GitHub Pages?
Although you can't use .htaccess or .conf, Github has instructions on how to use the Jekyll Redirect From plugin.
https://help.github.com/articles/redirects-on-github-pages/
The page above no longer has any mention of the plugin. The direct link to the jekyll-redirect-from plugin GitHub repo is https://github.com/jekyll/jekyll-redirect-from
"Unfortunately, GitHub pages only supports static pages. There is no way to make it execute server-side code and thus it's impossible to protect your pages with any kind of authentication scheme. If you expand further on why you need to password-protect your pages, maybe I can help you find a workaround."
Source: https://webapps.stackexchange.com/questions/35692/is-there-an-alternative-to-using-htaccess-to-password-protect-subdirectories-in
I'm using a 404.html to redirect users from old S9Y index.php to my new blog on Github Pages. Check this commit: https://github.com/lionello/lionello.github.io/commit/c175f6524a53e29aea1890c8a758afd0e8944852
This post comes out at the top of web search when you look for .htaccess redirects in github pages. I am going to answer this question in that sense.
One option is to use a DNS redirect instead. You do this by putting a file named CNAME in the project's root directory (not sure if it works in a subdirectory). Just put the redirection URL in the file. However, there are a few limitations, e.g. you can only redirect to a website's root.
The answer is yes you can now add "404.html" in you code Repository. You can display a custom 404 error page when people try to access nonexistent pages on your github site.
For more information you can refer to this link!
Note: I originally posted this on ServerFault, but I haven't gotten any responses at all. Since it looks like I'm on track to get the Tumbleweed badge over there, I figured I would try here also.
Our existing public website consists of a mish-mash of asp.net pages with mostly static content and some real web applications that are set up as virtual directories. We're now looking at installing Umbraco, which requires that you install it at the root of the website.
Since the CMS would be at the root of the website, I'm assuming it's a bad idea to run our existing pages and web applications underneath Umbraco (due to the URL rewriting it performs and inheriting web.config settings, etc.) So how do we make everything co-exist peacefully both while we transition to the CMS and after we're finished?
My only idea so far was to set up the CMS and the applications as separate websites and then use some sort of URL rewriting/reverse proxy to make everything resolve correctly:
* www.example.com would keep resolving to our old homepage
* www.example.com/dept1 would keep resolving to the old dept1 page
* www.example.com/dept2 would resolve to the new dept2 page on the CMS
* www.example.com/app would resolve to an existing web application
We ending up setting up Umbraco as it's own website in IIS and then we bought ISAPI Rewrite so that we could seamlessly pass through CMS content for certain URLs.