la.plume CMS Installation

la.plume Micro CMS is for use with web hosting packages running APACHE web server on Linux or FreeBSD and works best when .htaccess is supported and the mod_rewrite module is enabled. The CMS also requires PHP 5.2.0+. PHP is by far the most widely used scripting language for websites. More info »

Installation should take less than 2 minutes by following the simple instructions below. You will need an FTP client program to access your web server. FileZilla is free but there are many others. Can also be installed via cPanel.

Installation (version 10.4) in more detail

(1) Download

(2) Upload

Note. If you simply upload the laplume folder and everything inside it, your website will include /laplume/ in the site address. Normally you upload everything inside the folder to where you want it to run, not the folder itself.

Upload (FTP) everything inside* the download folder laplume to where you want the system to run. For example:

www.yoursite.comorwww.yoursite.com/subfolder/ ('subfolder' can be anything you want) orlocalhost/your-path/

Exclude contact.php if you don't want a contact page.

(3) Installation and Setup

You will need to setup passwords for (i) site 'admin' and also (ii) any password-protected pages you might create on your website. The same password will do for both but different ones are much better. Process passwords here or follow the instructions on the installation page. Don't forget the salt.

(0)755 is usually the directory default for web hosting services, and (0)644 for files - writable by you as owner. Directory and file permissions can be set in the File Manager of the website control panel (cPanel, Plesk etc).

The system is tested as fully functional. If you believe you have installed la.plume micro CMS correctly and something can be improved, don't walk away - please let me know via the contact page. Thank you. Patrick Taylor.

Tried it. Not to complicated to make it work and then works like charm! Very interesting approach to micro-cms, congratulations!

I'd like to take this chance to give some feedback too... It would make me less security concerned if content was separated from config/settings e.g. in different folders so security can be tightened more on settings and loosened on content. Some Web hosting servers I have encountered had different ideas how security shall work.

Thank you for sharing this solution, it is obvious that a lot of careful work was invested in this fine piece of web soft.

lj

Thanks for your positive comments, and the feedback too - though I'm not sure what you mean re security. Content is separated from config/settings (different folders).

Patrick

This is a pretty cool idea. Kudos

We're a group of volunteers and starting a new scheme in our community. Your site offered us with valuable info to work on. You've done a formidable job and our entire community will be grateful to you. | Bill Z Walton

Hi,
I love your CMS.
But i have a problem - / lists files instead of redirecting to
/cms/index.php
I tried to change htaccess, but without success.

Please advice
(same thing on local (wamp) and my host (arvixe))

Hmmm... I don't know. I have just installed the system 'out of the box' on a test server and it seems fine.

There are two files, "htacess.txt" and "htacess-laplume.txt" in the root of the cms folder structure, and both files contain that line:

"# Edit and save this file as .htaccess before uploading"

I didn't find anything about it in "CMS installation", so what should I do with that?
Thank you!

Could you please explain in details how this CMS works with joining up (sticking) the domains "www.site.com" and "site.com"?

The two files "htaccess.txt" and "htaccess-laplume.txt" are illustrative only (see above) for when the .htaccess file is set up manually. Normal setup creates the .htaccess file automatically. I will make this clearer in the next release.

Regarding joining up the domains "www.site.com" and "site.com" I am not sure what you mean by "joined up". Normally you would use one or the other, not both, and .htaccess can be edited to redirect the unused one to the one that is used but it would have to be done manually. I don't think it's critical.

Patrick

Thanks for answer!

As for domains I meant the search engine's attitude to the two variants of domain's writing: "www.site.com" and "site.com". I don't know the right English term for this process, but the essence is that the GOOGLE and other search services take these two form of domain's writing for two different sites. And as result, there may be some negative issues, such as taking one of the site's version for a duplicate(pinch) of itself but with another name (amazing!). That's why there must be a redirect rule for a search engine to regard these two variants of domain as one site (mirrors).

Excuse me my English, may be I'm explaining not clear enough... So, the main question is as follows:

Is the LaPlume CMS able to perform that operation with domains joining (junction), or should we make it manualy in the file .htaccess?

Thank you for your time!

I understand, and you are technically right. I don't think it matters much nowadays but if you want to be strictly correct then yes, you will have to do it manually in the .htaccess file... from www to non-www. or the other way round.

Patrick

Ok, thank you. I shall do it, most likely...

Also, I have a question about "robots.txt". The LaPlume CMS doesn't create it, so, how do you think, should I create it manually, and how the file affects SEO efficiency?

As you say, la.plume does not generate robots.txt. The reason is because the system has no knowledge of other things that may be on the same website so to avoid any possible conflict it's better without. It is easy to create manually if you want one. Regarding SEO, I don't think it's important but again, that might depend on what else is on the same website.

Incidentally (re .htaccess) you can also redirect lagraph.net23.net to lagraph.net23.net/laplume/ so that when you go to the address of the site, it doesn't start with the folder "laplume".

Patrick

Hello,
This is grand!

One question.
Is it possible to create vvv,seo,com/friendly/url-page/address ?
With your little wonder?

Thanking you.

forgive my english im from earth.

Hello. They already are.

For example this page (www.mini-print.com/CMS-installation) is friendly.

Note. The two files "htaccess.txt" and "htaccess-laplume.txt" (referred to above) no longer exist. The .htaccess file is now generated on setup.

nice

It would be nice if la.plume supported markdown. Please consider adding it. I would love it!

hello patrick submit comments showing error

Hello, and thanks, but what kind of error? When a comment is submitted you should see the following text at the bottom of the page:

Comments do not appear automatically. They are pre-moderated - you receive them by email then update comments in Admin. Other than that, maybe check the email address in setup? I received and added your comment so everything seems to be working.

If someone uses HTTPS, you can change the '/cms/admin/setup.php' file at top with something like this:

@Patrick: I have an update, for that workaround, because I saw there were other small issues (like the link in footer area), so, for those who don't have time to search&replace all files, I made a bash script:

This script will simply search&replace all http\:// with single or double quotes. Just run this script inside the main directory of laplume.

--

It's my second day with this CMS and the only thing I miss is the comment functionality... Why don't put the comments in quarantine text file mode, one comment per line coded with base64_encode (so the new lines won't be a problem)... If you have a small website, the actual method won't be a problem, but if you get fifty (or more) comments per hour it will be a big problem... :/

--
LC (wolfytuga.wordpress.com)

Thanks again. I agree that large numbers of comments might be an issue but I think some kind of moderation procedure is essential to block spam and other nonsense. And security when allowing anyone to edit a text file. But worth further thought.

Patrick

I have installed to a beta subdirectory of our society website to see if the rest of the committee are happy with the look and content of the website using la.plume. Now they are all happy I want to move the site from the beta directory to the root directory. Can I just copy all files on server from beta directory to root or is there further stages I need to complete?

Pete (sotcw.co.uk)

You can do it by copying all the files into the root directory and submitting setup again on:

... but probably a better way is to use the backup facility in admin and unzip everything onto your hard drive, backing up both the pages and images. Then install the system afresh in the root directory using the latest version 9.1. I would always recommend changing the name of the admin folder (for security), so the setup page would be:

www.sotcw.co.uk/cms/newadminname/setup.php.

Enter the settings as they were on your beta install then submit setup.

When you have the new install running to your satisfaction you can upload the files from your backup into the corresponding folders of the root install. Then in admin, update each page so that the menu file 'inmenu.txt' is updated (or just copy over 'inmenu.txt).

If you have edited the stylesheet you can paste it in to update styles in admin. The same with extra-content.php if you have added content to the extra div. Finally you will need to edit any internal links on your pages to remove the 'beta' directory from the path. That should be it. The main thing is to always make sure you have everything backed up.

Patrick

(Comment edited for Version 10.0, 5th Dec 2014)

thank you, very useful script

Hi Patrick

The htaccess file is missing from the rewrite folder in your latest laplume download. When I run install.php I get the message: Error. ./rewrite/.htaccess | missing in admin. Check you have all the files in the latest version of la.plume Micro CMS.