Title: webdev8183's Replies | WordPress.org --- # webdev8183 [ ](https://wordpress.org/support/users/webdev8183/) * [Profile](https://wordpress.org/support/users/webdev8183/) * [Topics Started](https://wordpress.org/support/users/webdev8183/topics/) * [Replies Created](https://wordpress.org/support/users/webdev8183/replies/) * [Reviews Written](https://wordpress.org/support/users/webdev8183/reviews/) * [Topics Replied To](https://wordpress.org/support/users/webdev8183/replied-to/) * [Engagements](https://wordpress.org/support/users/webdev8183/engagements/) * [Favorites](https://wordpress.org/support/users/webdev8183/favorites/) Search replies: ## Forum Replies Created Viewing 4 replies - 1 through 4 (of 4 total) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [youtube bg slider video not displaying on homepage](https://wordpress.org/support/topic/youtube-bg-slider-video-not-displaying-on-homepage/) * Thread Starter [webdev8183](https://wordpress.org/support/users/webdev8183/) * (@webdev8183) * [11 years, 12 months ago](https://wordpress.org/support/topic/youtube-bg-slider-video-not-displaying-on-homepage/#post-4981746) * Thank you I will head over there * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Can I replace images in DB with larger versions without breaking site?](https://wordpress.org/support/topic/can-i-replace-images-in-db-with-larger-versions-without-breaking-site/) * [webdev8183](https://wordpress.org/support/users/webdev8183/) * (@webdev8183) * [11 years, 12 months ago](https://wordpress.org/support/topic/can-i-replace-images-in-db-with-larger-versions-without-breaking-site/#post-4976329) * you could update the entries for filesizes in the database using MySQL that should cause it to update the corresponding attributes in the generated views. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Changing permalinks causes 500 Server Error](https://wordpress.org/support/topic/changing-permalinks-causes-500-server-error/) * [webdev8183](https://wordpress.org/support/users/webdev8183/) * (@webdev8183) * [11 years, 12 months ago](https://wordpress.org/support/topic/changing-permalinks-causes-500-server-error/#post-4855970) * do you have frontpage or frontpage server extensions installed? this looks like it might be relevant. Finally, A solution. * There have been a number of threads on this issue in the support forums, and until now, no solution to the problem. * Normally, on a Unix server with the Microsoft FrontPage Server extensions installed WordPress works just fine and you are able to edit and publish pages (with Microsoft FrontPage) — until — you make a change to the permalinks (for example to the date based kind that I like /2005/04/etc). I often suggest that type of URI to folks asking about permalinks etc, as that is the method recommended by the w3c( see [http://www.w3.org/Provider/Style/URI](http://www.w3.org/Provider/Style/URI)). * Now, the problem is that FrontPage uses the .htaccess file (which the WordPress mod_rewrite rules must access) for its “publishing” and “web authoring” configuration. As soon as the WordPress mod_rewrite code is added to the file, two things happen— the permalinks don’t work and the Frontpage Server extensions become corrupt. * I have tried countless ways to get around this, including trying to use rewrite rules that “ignore” the %{HTTP_USERAGENT)% used by FrontPage, to using a second AccessFilename .wpaccess to the httpd.conf file, and a host of other things, and nothing worked to allow use of FrontPage and management and use of permalinks in WordPress at the same time. * The solution is actually simple, and I figured it out by accident. * If you are using, or wish to use FrontPage (or if your hosting package is pre- configured that way) along with WordPress, you’ll need to take the following simple steps on your server or have your hosting company do them for you. * Microsoft FrontPage creates the following directory _vti_bin Nested within that it creates both _vti_adm and _vti_aut * In addition to in your site (or WordPress) root folder in all of those directories you will find additional .htaccess files. * In all three of these directories AND in the root directory, at the top of ALL of the .htaccess files you simply need to add one line: Options +FollowSymlinks * There may or may not already be a line in each like Options None * Edit and save each .htaccess file and you’re done. Now everything works perfectly, including FrontPage, AND the permalinks of your choosing. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Changing permalinks causes 500 Server Error](https://wordpress.org/support/topic/changing-permalinks-causes-500-server-error/) * [webdev8183](https://wordpress.org/support/users/webdev8183/) * (@webdev8183) * [12 years ago](https://wordpress.org/support/topic/changing-permalinks-causes-500-server-error/#post-4855968) * perhaps the actual error would help narrow down the cause, try adding that to your post, did you do a google search for the error you received cause sometimes that can help with diagnosing the cause. Have you also tried rebooting your modem? temporarily disabling security software? try the steps in this article [ I hope that helps you out, I can totally relate with how frustrating these issues can be especially when the computer doesn’t really tell you why its sick, it just is if you know what I mean Viewing 4 replies - 1 through 4 (of 4 total)