Is there a way to make github pages case insensitive?
Or in jekyll to ensure all url's are lowercase?
For example this url is valid:
http://www.example.net/Vegas-2014.html
but this 404s
http://www.example.net/vegas-2014.html
I don't like that from a usability perspective. (think text messaging urls, typing them in, etc.)
I know I can fix this with permalink, but I'm wondering if there is a way to do it through configuration of Jekyll or pages or some other technique.
Sorry but case-sensitiveness is a standard for URL that is respected in Unix/Linux world. Windows world in more case insensitive but it's another world ;-).
An Apache, Nginx or other open-source server is case-sensitive by default and can be configured to be case insensitive.
In the Jekyll/Github pages world, we must take care of our cases.
But maybe you can give try to Jekyll redirect from.
Related
I'm building a website, however the URL for the website is likely to change.
How can I load resources in the front end if the domain and installation directory is likely to change?
Now that I'm starting to get deep into building the backend I have some issues.
The url is about to change, what do I do now?
I can use PHP to get the current domain and have a preset installation directory. Then load it from a variable every time I need to load a resource.
Is there any other solutions, what would you recommend?
I'm talking about resources loaded through the browser, not ones loaded through php.
If the resources are housed under the same domain as your php app, you can simply remove the protocol and hostname from those links and let the browser figure it out.
If the resources are hosted on a different hostname (or via a different protocol - http vs. https for example) then your solution of using a variable is probably the best course.
I'm just started web developing not long ago, and I'm wondering why running HTML on my computer comes up with file:/// and then the file path and name in the browser url bar. For example, what I'm testing right now is:
file:///D:/WebDesign/HTML/test/default.html
Why isn't it file://, or just the pathname?
Is there a certain reason for this?
thanks for any answers.
// is part of the general format of URI schemes.
The next / comes after the optional — if defaults to localhost — hostname (since you can have a network path for file URIs).
See the Wikipedia article for more details.
It is a standard URL code for a local file. Also Check out this:-
the slash is a general, system-independent way of separating the
parts, and in a particular host system it might be used as such in a
pathname (as in Unix systems) or internally mapped to another
character
That is just standard URL code for a local file. A similar syntax is used to refer to a file on a network drive.
However, if you are attempting to develop like that you will run into problems, especially if you intend to test server-side functionality in languages like PHP. You may wish to look into installing a (free) program such as XAMPP or WAMP/MAMP that will emulate an apache server and allow you to test these things.
You can find some very helpful (free) tutorial videos here
Look at the first three videos here
And here's another that discusses installing XAMPP/WAMP
Found an interesting article about "Cruftless" links (removing the "index.html" from links) but when I do that no browser shows the local pages.
http://www.nimblehost.com/blog/2012/11/why-cruftless-links-are-better/,
This is understandable, it's a 'file' url from a local machine, so what do people do to work on basic html sites offline? How do they preview them?
For example, no browser (understandably) will display this...
file:///JOBS/ABC/About/
... but this is fine...
file:///JOBS/ABC/About/index.html
?... so what do people do to get around this?
The meaning of file: URLs is, by definition, system-dependent. Normally browsers map them to files in the file system in a relatively straightforward manner.
Thus, a link with href value like file:///JOBS/ABC/About/ may or may not work, depending on system. It may fail, or it may open a generated document containing a directory (folder) listing, or it might do something else.
There is normally no need to get around this, and it is pointless to worry about SEO when dealing with local files.
This could, however, matter during site development when you work with a site locally (and perhaps test and demonstrate it locally). Then you might wish to have, say, About us so that it works locally as well as on a server, yielding About/index.html in both cases but without hard-wiring index.html in HTML markup.
I’m afraid the answer is “you can’t”. But as a workaound, you can install and use a local HTTP server, with settings similar to those that you will have on the real server. This means a little extra work (mainly downloading and installing and configuring software like XAMPP), but it also gives you important other benefits, like testing your pages locally with server-based features (to the extent that the real server is similar to the local server).
I would like to know your opinion on developing a .html web pages site using code igniter? Is it good to develop static sites/pages.html using CI?
I am considering this for developing a secure static site. often my website is attacked by spammers (injecting external code put in and redirects to some other sites) etc.,
Also thinking to implement better SEO with CI.
what do you think experts?
Developing a complete static website in CI with just HTML pages is going way too overboard. Using a framework does not automatically take care of all security issues - it just makes it a lot easier to handle rudimentary security related issues with user input.
If there will be no server side or database interaction, the scope of your security will be limited to the server on which you're hosted on (and your passwords obviously).
SEO with static pages will not be better than the CI counterpart and vice versa. This will be entirely up to how you code the site and what sort of relevant data you offer and other various external variables that are associated with SEO (like in bound links). However, a static website, implies static content, which in turn implies slow updating of content or lack thereof - which search engines hate.
you need to remove those XSS code
did you already try this php function strip_tags()? you can also exclude html tags from being stripped ie. $commentmessage = strip_tags($commentmessage,'<img><a>');
here's my website:
www.newportclassic.com
do you know of any free, easy to use, content management systems, that will allow me to simply edit the text on my site without having to download the file, open the file, edit the code, save the file, upload the file ???????
I know of a few CMS's that have done well, here are two of them.
Wordpress - free - http://wordpress.org/ - 3.0 is coming soon
Perch - paid - http://grabaperch.com/ - very light and easy
Wikipedia has a very good list of content management systems broken down by language and cost (open source/proprietary) and DBMS. Most of the ones I've used/evaluated in the past have been .NET based, such as DotNetNuke. Pretty much any CMS will give you the ability to edit your HTML without changing any files on your web server. If you're going for simplicity, the Wikipedia list has several that use a flat file instead of a database, so I would start there: http://en.wikipedia.org/wiki/List_of_content_management_systems#File_.2F_Flat_file
As an alternative to installing a CMS on your server, you might be interested in a service like CushyCMS. It allows you to specify what parts of your page are editable by setting an appropriate class in each editable div tag. Then to edit the contents of those div blocks, you log in to the CushyCMS site and make your changes right there. CushyCMS connects via FTP to the server for you and updates the HTML page.
You can use emacs -- it has a mode (tramp) where you can open, edit and save remote files as if they were on your local machine. This makes it really easy to edit files on a webserver.
haven't used it myself but i've heard Surreal CMS is quite good and easy to setup. Here's a tutorial to get you started.
In terms of user friendliness zimplit is hard to beat.
Try their demo.
You can literally edit your website with a wysiwyg interface inside your browser.
Refinery HQ is probably the easiest way to create, edit and update your website. You can upload images and files as you describe in your question.
You can also connect it to your own domain (it's a hosted service). So you'd be able to hook the site you create up to newportclassic.com