Title: carestad's Replies | WordPress.org

---

# carestad

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [Use of localization functions within register_taxonomy in functions.php](https://wordpress.org/support/topic/use-of-localization-functions-within-register_taxonomy-in-functionsphp/)
 *  Thread Starter [carestad](https://wordpress.org/support/users/carestad/)
 * (@carestad)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/use-of-localization-functions-within-register_taxonomy-in-functionsphp/#post-4913960)
 * And the **after_setup_theme** hook didn’t work. I had to use **init** for the
   function that calls `register_taxonomy()`.
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [Use of localization functions within register_taxonomy in functions.php](https://wordpress.org/support/topic/use-of-localization-functions-within-register_taxonomy-in-functionsphp/)
 *  Thread Starter [carestad](https://wordpress.org/support/users/carestad/)
 * (@carestad)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/use-of-localization-functions-within-register_taxonomy-in-functionsphp/#post-4913957)
 * Oh God, feel like such an idiot now. In my functions.php i had:
 *     ```
       load_theme_textdomain('foo', get_template_directory() . '/languages');
       load_child_theme_textdomain('foo', get_stylesheet_directory() . '/languages');
       ```
   
 * Changing it to
 *     ```
       load_theme_textdomain('foo', get_template_directory() . '/languages');
       load_child_theme_textdomain('bar', get_stylesheet_directory() . '/languages');
       ```
   
 * And adding the textdomain as a second argument to the `_e()` and `__()` functions
   made it work (`'name' => __('Genre', 'bar')`).
 * Thanks!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[StatPress] WP_DEBUG causes PHP warnings](https://wordpress.org/support/topic/wp_debug-causes-php-warnings/)
 *  [carestad](https://wordpress.org/support/users/carestad/)
 * (@carestad)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/wp_debug-causes-php-warnings/#post-4242758)
 * Yes, and the use of eregi() is also deprecated in newer PHP versions, so please
   fix this
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Media File Renamer: Rename for better SEO (AI-Powered)] PHP: Parse error: syntax error, unexpected T_ELSE](https://wordpress.org/support/topic/php-parse-error-syntax-error-unexpected-t_else/)
 *  [carestad](https://wordpress.org/support/users/carestad/)
 * (@carestad)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/php-parse-error-syntax-error-unexpected-t_else/#post-3318753)
 * Oh, it’s because you’ve used short open tag in PHP one place. Some versions of
   PHP disables the use of short open tags. Just replace the
 * `<? if ($flagged > 0) { ?>`
 * with
 * `<?php if ($flagged > 0) { ?>`
 * on line 299 in **media-file-renamer.php**.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Media File Renamer: Rename for better SEO (AI-Powered)] PHP: Parse error: syntax error, unexpected T_ELSE](https://wordpress.org/support/topic/php-parse-error-syntax-error-unexpected-t_else/)
 *  [carestad](https://wordpress.org/support/users/carestad/)
 * (@carestad)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/php-parse-error-syntax-error-unexpected-t_else/#post-3318744)
 * Isn’t the new version updated in SVN? I just downloaded the plugin and I’m getting
   the same error when trying to activate the plugin in WP.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Post Requirements] [Plugin: Post Requirements] Parse error](https://wordpress.org/support/topic/plugin-post-requirements-parse-error/)
 *  Plugin Author [carestad](https://wordpress.org/support/users/carestad/)
 * (@carestad)
 * [13 years, 8 months ago](https://wordpress.org/support/topic/plugin-post-requirements-parse-error/#post-3080661)
 * Ah. This is most likely becaus I’ve used a syntax for lambda functions that are
   only supported in PHP 5.4. I’ll try and change this for backwards compatibility.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [2.8.1 CodePress Syntax Highlighting Removed?](https://wordpress.org/support/topic/281-codepress-syntax-highlighting-removed/)
 *  [carestad](https://wordpress.org/support/users/carestad/)
 * (@carestad)
 * [17 years ago](https://wordpress.org/support/topic/281-codepress-syntax-highlighting-removed/#post-1140079)
 * I think they should try and find something else than CodePress. It hasn’t been
   developed in ages and doesn’t work that well these days.
 * What about a switch to EditArea ([http://tr.im/viMi](http://tr.im/viMi))?

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