Title: akalt's Replies | WordPress.org

---

# akalt

  [  ](https://wordpress.org/support/users/akalt/)

 *   [Profile](https://wordpress.org/support/users/akalt/)
 *   [Topics Started](https://wordpress.org/support/users/akalt/topics/)
 *   [Replies Created](https://wordpress.org/support/users/akalt/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/akalt/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/akalt/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/akalt/engagements/)
 *   [Favorites](https://wordpress.org/support/users/akalt/favorites/)

 Search replies:

## Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Feeds broken after Upgrade to 1.2.1](https://wordpress.org/support/topic/feeds-broken-after-upgrade-to-121/)
 *  Thread Starter [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/feeds-broken-after-upgrade-to-121/#post-98129)
 * OK, solved it.
    I had to update the contents of my .htaccess file. The rewrite
   rules were different in 1.2.1 although my URL-structure hadn’t changed.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Feeds broken after Upgrade to 1.2.1](https://wordpress.org/support/topic/feeds-broken-after-upgrade-to-121/)
 *  Thread Starter [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/feeds-broken-after-upgrade-to-121/#post-98128)
 * After a re-install, the Opera login problem is gone.
    And I homed in on the feed
   problem. In index.php the following code is my feed link: `<?php bloginfo('comments_rss2_url');?
   >` This spits out the following URL: [http://www.andreas-kalt.de/blog/feed/rss2/](http://www.andreas-kalt.de/blog/feed/rss2/)
   There is no feed available under this URL. There is one, however, under [http://www.andreas-kalt.de/blog/wp-rss2.php](http://www.andreas-kalt.de/blog/wp-rss2.php)
   Any ideas of what might have gone wrong with the upgrade?
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Feeds broken after Upgrade to 1.2.1](https://wordpress.org/support/topic/feeds-broken-after-upgrade-to-121/)
 *  Thread Starter [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/feeds-broken-after-upgrade-to-121/#post-98114)
 * I just noticed that a feed is available when I call
    wp-rss2.php However, my 
   old feedlink got converted to this address: /feed/rss2/ The login problem with
   Opera still is a mystery.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Feeds broken after Upgrade to 1.2.1](https://wordpress.org/support/topic/feeds-broken-after-upgrade-to-121/)
 *  Thread Starter [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [21 years, 7 months ago](https://wordpress.org/support/topic/feeds-broken-after-upgrade-to-121/#post-98113)
 * I did.
    Two strange things happen: 1. Some signs are not encoded, e.g. the umlaut“
   u” turned up as a diamond with a question mark and the Â° in the Geo info was
   a question mark 2. I can log on with Firefox and IE but not with Opera.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Empty categories visible in 1.0.1](https://wordpress.org/support/topic/empty-categories-visible-in-101/)
 *  Thread Starter [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [22 years, 3 months ago](https://wordpress.org/support/topic/empty-categories-visible-in-101/#post-32007)
 * Actually, I just realised that I used the latest nightly (2004-1-23) – so the
   bug is still there in the latest version.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Empty categories visible in 1.0.1](https://wordpress.org/support/topic/empty-categories-visible-in-101/)
 *  Thread Starter [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [22 years, 3 months ago](https://wordpress.org/support/topic/empty-categories-visible-in-101/#post-32006)
 * Actually, I just realised that I had used the latest nightly (2004-1-23) – so
   the bug is still there in the latest version.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Empty categories visible in 1.0.1](https://wordpress.org/support/topic/empty-categories-visible-in-101/)
 *  Thread Starter [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [22 years, 3 months ago](https://wordpress.org/support/topic/empty-categories-visible-in-101/#post-32005)
 * Thanks.
    Just to clarify: if I upgrade, do I always have to replace all files
   in the WP directory? Sure there must be away of keeping all my customisations
   and not having to add them back in after the upgrade? Andreas
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Last updated links doesn’t work](https://wordpress.org/support/topic/last-updated-links-doesnt-work/)
 *  Thread Starter [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [22 years, 3 months ago](https://wordpress.org/support/topic/last-updated-links-doesnt-work/#post-31941)
 * With this in place, I get a parse error:
    : parse error, unexpected T_STRING,
   expecting T_VARIABLE or ‘$’ in on line The top of my index.php looks like this:
   <?php /* Don’t remove these lines. */ $blog = 1; require_once(‘wp-blog-header.
   php’); include_once(ABSPATH.WPINC.’/links-update-xml.php’); ?> <!DOCTYPE html
   PUBLIC “-//W3… … I’d appreciate another hint… Thanks. Andreas
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Quicktags in Opera work like doody](https://wordpress.org/support/topic/quicktags-in-opera-work-like-doody/)
 *  [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [22 years, 3 months ago](https://wordpress.org/support/topic/quicktags-in-opera-work-like-doody/page/2/#post-31863)
 * Sorry, I forgot to escape the tag brackets.
    Againg: “+s” will be ** etc.**
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Quicktags in Opera work like doody](https://wordpress.org/support/topic/quicktags-in-opera-work-like-doody/)
 *  [akalt](https://wordpress.org/support/users/akalt/)
 * (@akalt)
 * [22 years, 3 months ago](https://wordpress.org/support/topic/quicktags-in-opera-work-like-doody/#post-31862)
 * About having to type everything by hand:
    try ShortCut ([http://www.typer.de/](http://www.typer.de/)).
   I configured it to give me all the tags I want at a few simple key combinations.
   E.g. “+s” will be **, “+ss” will be ** and so on. It really speeds things up.

Viewing 10 replies - 1 through 10 (of 10 total)