wordpress do-over…

Not sure reinstalling WordPress would fix either of those issues. A favicon is not included so you’d just need to ensure that your own favicon is in your site root.

In a similar way, pretty permalinks should work for whatever install. Try setting back to default, then back onto pretty. Make sure you have mod rewrite enabled. (See https://www.debuntu.org/2006/06/15/66-how-to-enable-apache-modules-under-debian-based-system )

ty mrmist,

i will look into that “how to” link. also, the favicon has somehow started working on its own as a result of my tinkering with things.

Also make sure that you have the WordPress rewrite rules in your .htaccess file. Otherwise “pretty” or “custom” permalinks will not work.

hahaha!!!! ty skipper!!!

here is one of my original posts about this issue and some of the things i tried. https://www.ads-software.com/support/topic/367029?replies=3

i feel i need to move to the left on this issue as mrmist has articulated; perhaps even do away with the .htaccess file all together by transcribing the .htaccess rule into apache2.conf then set “AllowOverride none”. which is recommended under the apache2 docs for greater security and performance. although i cannot find the ref to this advice at present.

i consider eliminating .htaccess an advanced maneuver at this time and feel that everything should be working before i attempt to tune things in this way.

i have to read the “how to” given by mrmist a few more times before i try to use it.

i hope to mark this issue resolved soon. ??

@mrmist,

i already have rewrite enabled and it still does not work…

bubba:/home/af# a2enmod
Your choices are: actions alias asis auth_basic auth_digest authn_alias authn_anon authn_dbd authn_dbm authn_default authn_file authnz_ldap authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cern_meta cgi cgid charset_lite dav dav_fs dav_lock dbd deflate dir disk_cache dump_io env expires ext_filter fastcgi file_cache filter headers ident imagemap include info ldap log_forensic mem_cache mime mime_magic negotiation php5 proxy proxy_ajp proxy_balancer proxy_connect proxy_ftp proxy_http rewrite setenvif speling ssl status substitute suexec unique_id userdir usertrack version vhost_alias
Which module(s) do you want to enable (wildcards ok)?
rewrite
Module rewrite already enabled
bubba:/home/af# sudo /etc/init.d/apache2 reload
bash: sudo: command not found
bubba:/home/af# /etc/init.d/apache2 reload
Reloading web server config: apache2.
bubba:/home/af#

@skipper,

here is the contents of .htaccess…

# BEGIN WordPress
Options +FollowSymLinks
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Custom Permalinks is set to /blog/%postname%/

this is the url.

As far i can tell your WordPress installation is in a directory called WordPress, is the htaccess file in the WordPress folder or on in the root?

Assuming in the WordPress folder, the rules above look fine, if the htaccess is in the root, you’re missing the directory in the rules.

Might not be any help at all, just felt it worth a mention.

RESOLVED!!!

ty t31os_

after moving .htaccess with contents given above into /home/web/wordpress and adding `# For wordpress
<Directory />
Options FollowSymLinks
AllowOverride All
</Directory>

<Directory /home/web/wordpress>
# … other directives…
AllowOverride All
</Directory>
`
to /etc/apache2/httpd.conf then restarting apache apache2ctl restart it appears that pretty custom permalinks is now working.

??

Not exactly what i meant, but if it led you to the solution then that’s great, and i’m happy to have helped.. ??

also, part of the problem may have been that some who i trust in my server forum ~assured~ me that “AllowOverride” directives were suppose to go in /etc/apache2/apache2.conf rather than /etc/apache2/httpd.conf. one solution was to place said directives into the latter file.

it may be that AllowOverride directives can indeed be placed into /etc/apache2/apache2.conf but since it works in /etc/apache2/httpd.conf as advised in the wordpress codex i will not change it.

indeed your proposal led me to the solution. i had not considered that .htaccess should reside in the same location as wordpress subsequently it was in the directory above wordpress.

oh happy day!!! ??

Well it doesn’t necessarily need to be in the WordPress directory, but if it’s in the one above, the rewrite rule should contain the directory path.

ie.

RewriteBase /

RewriteBase /wordpress/

ty for that tip too. i think that your suggestion was the missing piece of information.

at present i would like to eliminate the /wordpress/ from display after my url in the location box.

i am reading the codex section on how to move the site.

can i just move everything up a level and delete /wordpress/? would i have to adjust my database?

should i try this and then start another thread if i fail?

For moving WordPress.
https://codex.www.ads-software.com/Moving_WordPress

And yes i’d probably suggest a new thread, since it’s a seperate discussion.