Can quotation marks (double quotes and single quotes) and apostrophes be included in your WordPress permalink URLs? I am not an authority on this, but I found a case recently where an apostrophe from a post title was being included in the permalink and it was causing the permalink to produce a “Page Not Found” 404 error. Removing the apostrophe from the permalink fixed the problem.

By the way, if you are looking for a solution to the problem of multiplying apostrophes and quotes in your WordPress posts, click here: How to Fix WordPress Multiple Apostrophe.

The example looked something like this. This is not the actual URL and title, but it did include “Montezuma’s Revenge”. Maybe that’s what the server found offensive!

http://www.example.com/2009/blah-blah-montezuma’s-revenge-blah-blah/

The title of the post was “Blah Blah Montezuma’s Revenge Blah Blah” (without the double quotes).

As you probably know, you can put apostrophes and quote marks in post and page titles, but if your site is hosted on WordPress.com, those will be removed when WordPress creates the permalink URL. [UPDATE: No. Double quotes will not necessarily be removed, as you can see from the URL for a recent post on WordPress Security.]

The problem with an apostrophe in a URL happened on a self-hosted WordPress installation, and, as a matter of fact, it is installed on a Windows IIS server, rather than the usual Linux/Unix Apache server.

I’m not an expert at server issues, but I do know that sometimes things like this happen with WordPress only on Windows servers. For instance, when you enable permalinks on Windows, sometimes the URLs will include “index.php” – like http://www.example.com/index.php/2009/blah-blah-montezuma’s-revenge-blah-blah/ when this normally never shows up in a URL.

At any rate, when I used the Permalink Edit button (under the post/page title window in the WordPress Editor) to remove the apostrophe, the problem went away. The permalink URL now looks like: http://www.example.com/2009/blah-blah-montezumas-revenge-blah-blah/

Oddly enough, I can now get to the page from both URLs

http://www.example.com/2009/blah-blah-montezumas-revenge-blah-blah/

and

http://www.example.com/2009/blah-blah-montezuma’s-revenge-blah-blah/

No idea why that would be, but who cares since there’s no longer a 404 error.

ik kan er niets aan doen, maar telkens ik dat woord zie staan, moet ik twee keer kijken om dan telkens weer te weten dat het niet, ik herhaal niet, spermalink is, maar permalink.

onthou het nu, geiltje!

Langkah-langkah mengubah permalink sesuai keinginan
Pada kesempatan kali ini akan dibahas mengenai bagaimana cara mengubah struktur permalink dalam webblog atau blog anda khusus yang menggunakan wordpress. Perubahan ini dilakukan agar Search Engine lebih berhasabat dan bebas dari masalah.
Jika anda membuat weblog hal pertama anda perhatikan adalah struktur pemalink. Biasanya standard permalink adalah http://namablog.com/?p=123 hal ini sangat tidak familier dalam search engine karena nama halaman tidak memuat informasi mengenai isi didalamnya. Jadi yang anda lakukan adalah mengubah struktur permalink menjadi /%category%/%postname% atau bahkan hanya /%postname% saja. sehingga pada url posting blog akan tampil http://www.namablog.com/kategori/judulposting atau http://www.namablog.com/judulposting . Hal ini akan sangat mempengaruhi hasil dari SERPs (search engine result pages).
Nah yang jadi pertanyaan adalah bagaiamana jika kita terlanjur membuat halaman atau postingan, yang permalinknya standard? Berikut ini langkahnya :
1. Ubah permalink anda melalui SettingsPermalinks Kemudian pilih custome struktur, kemudian isi seperti : /%category%/%postname atau /%postname saja.
2. Setelah anda merubah permalink maka secara otomatis akan ada peringatan yang mengharuskan anda mengubah file .htaccess. Klik save setting.
3. Ubah permission file .htaccess dari nilai 644 (read only) menjadi 755 (rewriteable) . File .htaccess berada di /public_html/.htaccess . Cara nya menggantinya bukalah control panel domain anda dengan membuka http://namadomainanda.com/cpanel. Masukan username dan password kemudian pilih menu file manager. Dari file manager anda pilih public_html dan cek lah pilihan/opsi hidden file. Setelah itu klik kanan file .htaccess pilih change permission klik opsi Tanda cek hingga nilainya menjadi 755. Klik Ok jika sudah selesai. Baca disini untuk lebih lengkap tentang pengubahan permission. Artikel lengkap downlod disini

Se hai un blog wordpress, e intendi ottimizzarlo al meglio, in particolar modo in ambito SEO (search engine optimization), il primo consiglio che personalmente posso darti è: fai attenzione ai Permalink…

Cosa sono i Permalink?
In pratica ogni post (articolo) all’interno del nostro blog (wordpress), presenta un indirizzo url, esempio:

http://www.tuoblog.com/abcdefg/123213/articolo-di-prova
Tale url si chiama Permalink

Ora, ti starai chiedendo:
ma come posso fare per ottimizzare i Permalink nel mio blog wordpress, e trasformare un url tipo:

http://www.tuoblog.com/abcdefg/123213/articolo-di-prova

in

http://www.tuoblog.com/articolo-di-prova

così da rendere il post Seo Friendly?

Puoi farlo emplicemente agendo nelle impotazioni di WordPress, sotto la voce Permalink, e inpostando un valore personalizzato, identico a questo:

/%postname%/

ovviamente barre e percentuali comprese

Ho già provato personalmente questa tecnica, e in effetti aiuta parecchio il blog e la sua indicizzazione nei motori di ricerca, anche se si tratta di una piccola modifica, è da tenere presente che è importantissimo effettuarla fin dall’infanzia di un blog, in fondo si tratta di una cosetta da 10 secondi… 

Here’s something that should really be useful to all of you prolific reviewers out there: you can now get a permalink to any one particular review that you can share with your friends. Rather than have to scroll through dozens (or hundreds!) of your reviews, they can quickly and easily get to the exact movie review you choose.

For example, here’s my review page with a review of Match Point:

Movie Reviews Page

Now, under each review, you’ll see a permalink to that particular review. The permalink for my review of Match Point happens to be: http://feedfliks.com/r/97bcda61b532440734613327d68e8b1baa54a47d

Click on this and you’ll get a page that shows just that review:

Review Permalink Page

This link (http://feedfliks.com/r/97bcda61b532440734613327d68e8b1baa54a47d) will always work even if you go back and make edits to your review. It’s super-easy now to share your favorite review on Twitter, Facebook, Email or on  Blogs.

Using the 5 minute install directions, I made a remote install to mess around with WordPress remotely. Adding themes and plug-ins are extremely easy, so I am just fooling with the interface. My brother-in-law wants a portfolio site, so I am making him one in WordPress as well. I may or may not post the link: not sure if I should just post about one site in this blog. However, any lessons learned will definitely be posted here.

While changing themes, I decided to add a permalink to one of the pages; this is a similar concept to search engine friendly links in Joomla! However, when I did this, I got a 500 error on my server. From what I can tell, I should not have tried to add a permalink without first configuring the .htaccess file. I have read through this article 5 or 4 times, but still cannot quite figure out what I need to change in the file. Moreover, I cannot access my site backend due to my error. This is no big deal since I was just playing with the interface, so if I have to delete it all and start over, I am not too worried. I do want to figure out how to add permalinks and will continue to work on this.

UPDATE:

I have tried numerous things to make this work, but am still at a loss.

The root issue seems to be that whenever an .htaccess file is added to my server–with countless iterations–I get a 500 error; I even get an error when using the method from within the WordPress Dashboard (Settings>Permalinks): this method also creates an .htaccess file on the server. This makes me think my host does not allow them, although my contact at the company seems to think it is allowed. Therefore, I put in a trouble ticket on this issue today. The issues is hard to decipher since I don’t have control panel access to my account…

YET ANOTHER UPDATE:

This issue has to do with my host. I tried to enact permalinks using the method shown below on another host–hostgator–and was able to get it to work properly:

The lesson I learned is that if you try to enact permalinks in this manner and your site–and admin–have a 500 server error, your host probably does not like your .htaccess file created by WordPress. To get your site back, FTP to the folder your installation resides, make sure to enable ‘Show Hidden Files’ in your FTP client, and delete the .htaccess file. From there, your site and admin login will reappear.

Ieri, 21 august 2009, la ora 00:01 am dat ultimul save la noua noastra platforma de development, e-media. De fapt este mai mult decat platforma de development, este o platforma media, pentru ca, in definitiv pentru asta a fost facuta – sa poata sustine mai mult decat un site: un canal media.

E-media este in acelasi timp o platforma tip CMS dar si o platforma de e-commerce, permite dezvoltarea rapida a unui site extrem de simplu, a unui site complex de continut, a unui catalog sau magazin virtual dar si a unui site 100% customizat.

Pentru designeri si developperi are toate avantajele unei platforme OS – usurinta in instalare si configurare, fara sa anuleze cu nimic libertatea de a face orice in site, cu minim de efort. Iar pentru client, asta inseamna timp si bani: customizarile dincolo de limitele aplicatiei sunt la fel de simple (si de ieftine) ca si cele din interiorul acestori limite, dintr-un simplu motiv: aceste limite nu exista.

Suplimentar, permite scriere de cod PHP direct din aplicatia de admin, contine un crawler propriu, din care rezulta pe de o parte un motor de cautare rapid (cei care stateau 2-3 secunde pentru un rezultat stiu de ce!) si cu rezultate relevante (cu indice de relevanta definit chiar de noi) ci si un sistem de raportari pentru broken links, missing images, external links samd.

Interfetele sunt si ele dezvoltate cu gandul la viitor, fara a neglija, ci de fapt incorporand experienta noastra de peste 9 ani in domeniul web design & development.

SEO a fost o alta preocupare importanta in dezvoltarea platformei. Totul, dar absolut totul, a fost gandit tinand cont de implicatiile SEO ale fiecarei optiuni. Iata cateva aspecte: permalinks pentru pagini, categorii, produse; custom url pentru imagini; alt-uri pentru imagini, utilizarea tag-urilor h1, h2, h3; metatag-uri definibile pentru fiecare pagina, categorie sau produs (bineinteles); sistem de cautare si afisare care elimina url-uri multiple pentru aceeasi pagina (am preferat actualizari ajax in locul link-urilor cu variabilelor de tip page.php?a=5); variabile transmise integrat in url dar numai cand sunt generate pagini distincte; permalinks pentru rezultatele de cautare.

Desi ma voi opri aici, lista de facilitati continua si o voi detalia, probabil cate un set pe postare.

De luni e-media intra intr-un proces de testare si finisare, va avea in curand un site dedicat si vor incepe implementarile de test.

If you’ve read my blog before, you know that academic honesty is very important to me, both for the sake of developing personal integrity, and for the sake of recognizing and valuing the work of others.

The fluid, fluctuating nature of online communication makes it hard to consistently define and uphold academic honesty. It’s hard to define what respect of intellectual property looks like on a blog, for example, or a website, or a MySpace page.

Should all bloggers be required to use MLA citations when they quote a fellow blogger? Do permalinks make it acceptable to reproduce an entire post or article on your own site? What about images?

These questions can be overwhelming. One of the dangers of online communication is that too much information–and too little–can lead to carelessness and apathy. “No one told me I had to cite that image from Google Images. There’s no guide for quoting a website on another website, so I didn’t bother.”

Personal responsibility is out of vogue in our era. We like step-by-step instructions, and if the warning label “hot” isn’t on the cup of coffee, we have every right to legal restitution.

I am as guilty as the next person. In writing this blog, I have attempted to develop my own system of ethical use guidelines for quoting and “borrowing” others’ content. When I quote a blog or online article, I use the “blockquote” feature, and I include a permalink to the source. When I use an image to supplement my text, I link the image back to its source rather than to my site.

Is that the best way to do it? Probably not. Could I do more? Yes. Should I? I’m not sure. But am I freed of responsibility because there is no one right way to do it? Absolutely not.

Cracking down on Internet piracy and protecting copyrights have cost the writing, publishing, film making, and music industries enormous effort, and have done little to stem the flood. Smart people circumvent the system every day. Smart people will continue to find new ways around the new protections designed by other smart people.

The only way that real change will occur is when smart people take responsibility and choose to be honest people.

Unfortunately, if that sounds over-simplified, it is. Our postmodern view that all ethical systems are equal has made it easy to justify downloading pirated music (“Hey, I wasn’t the one who posted it!”) or leaving out the quotations marks once in a while (“It’s only Wikipedia; I could have written the same thing.”).

It’s a slippery spiral, isn’t it?

Relativism is only attractive until someone else’s ethical system interferes with us; until we write something and see it spread over the Web without our permission; until we cry “not fair” and no one listens.

So where do we go from here?

In blogging, just as much as in college classrooms, I think it is worth considering what honesty means, on what it is based, and how we erode it, or build it up, in each choice we make and webpage we open.

Buat para pengunjung… situs ini untuk selanjutnya saya pindahkan ke alamat baru http://kamalsy.com.

Silakan berkunjung… semoga di tempat baru ini anda akan lebih memberi manfaat…

Salam online,

K-mal

I was searching some keyword in Google.com and I found a little bit different in SERPs, Yeah… Google SERPs is changing now. Some permalink with many characters will cut by Google with this sign “…”. SERP’s just only show to you about what you are looking for as keywords.

I think it’s one significant of innovation by Google. Google search engine just show to you relevant information about keyword. It’s a vision by Google in which bring us a quite touch of relevant searching in search engine.

A million peoples was use search engine to looking for some information, and that’s why Google always improve their search engine. Bring to you the accurate information about what you are searching is a vision by Google.

Unique content with true information and accurate news is a couple factors why we should use search engine like Google.

1. Judul tulisan sebagai PERMALINK lebih baik dicheck dulu di KEYWORD supaya tidak sia sia menulis judulnya.

2. Pintar dalam memilih TAGS agar sesuai dengan apa yang dicari SEARCH ENGINEE (minimal 8 tags).

3. Link-kan dengan SOCIAL BOOKMARKS

4. Posting di WEBIKLAN yang PRnya tinggi dan ALEXAnya yang <100 ribu, karena ini bagian juga dari BACKLINK (pasang minimal 100).

5. Baru BLOGWALKING dan SHOUTBOX, yang Bombastis dan Penasaran sehingga dibaca.

6. Bisa ditambahkan di Kaskus, Oktavita, Artikelmu dll.

Dari cara diatas kami bisa PR4 dan Alexa 200 ribu plus rata rata kunjungan blog 600 hits.

Sukses selalu buat semuanya, 081 333 841183, 0817 537894, 0341 5455330

Bagaimana menghilangkan “index.php” dari URL aplikasi CI ?.Hanya menyembunyikan saja tidak menghilangkan fungsi “index.php” sebagai front controller aplikasi CI. Jadi meskipun tidak nampak lagi di URL file sendiri masih harus tetap ada di direktori root CI.

Hal tersebut dapat dilakukan dengan membuat file .htaccess yang di dalamnya berisi ruleset direction untuk web server dalam hal ini adalah apache.

Langkah-langkahnya adalah sebagai berikut :
misal diasumsikan kita menggunakan OS Windows dengan XAMPP terinstal di C:/xampp. dan file CI kita taruh di C:/xampp/htdocs/tes/ci_mod_rewrite/

1. Buat file .htaccess.
2. Rubah isi variabel konfigurasi $config['index.php'] = ”;
3. Pastikan modul mod_rewrite apache ada dan sudah dikonfigurasi.

Berikut isi file .htaccess-nya :

Options FollowSymLinks

<IfModule mod_rewrite.c>
	RewriteEngine on
	RewriteRule ^([a-zA-Z0-9\-\_/]*)$ /tes/ci_mod_rewrite/index.php?$1/ [L]
</IfModule>

file source nya berisi file CI + file .htaccess = download