tela
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Visual Rich Editor Not AppearingI had the same problem too. The visual rich editor wouldn’t appear on a new install of v2.0.2. It didn’t work on Firefox, neither IE.
Kris_f’s post hint me to check Firefox’s Javascript Console. I didn’t get the same error than Kris_f though. In my case it stated:
illegal character in tiny_mce_gzip.php on line 223
tinyMCELang['lang_bold_img'] = \"bold.gif\"
Illegal character pointed to the double quote.I retrieved this line in wp-includes/js/tinymce/langs/en.js:
I used single quotes instead of double quotes. I actually changed for these 3 items:
tinyMCELang['lang_bold_img'] = 'bold.gif';
tinyMCELang['lang_italic_img'] = 'italic.gif';
tinyMCELang['lang_underline_img'] = 'underline.gif';
That solved my problem. Hope it can help somebody else too.Forum: Fixing WordPress
In reply to: Unresolved Permalink IssueI was having the same problem too and that how I fixed it.
Apache doesn’t recommend to use the .htaccess files anymore as they pose some security risks and are slow anyway.
In httpd.conf:
# Normally, you already have a very restrictive set of features for all directories
# that Apache has access to.
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
Now you can ask your webhost to add this, considering that
all WordPress sites are located under this directory
structure: /var/www/*/wordpress:
(your main index.php being in /var/www/*/wordpress)
# This is needed for permalinks to work
# on WordPress without using .htaccess files
<Directory /var/www/*/wordpress>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
</Directory>