WordPress.org

1. MattiasP
   Member
   Posted 5 months ago #

   I get this message when activating Advanced Excerpt:

   Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in .../wordpress/wp-includes/functions.php on line 3468

   And this belong the plugin title:

   The plugin generated 284 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

   Or am I doing something wrong?

   http://wordpress.org/extend/plugins/advanced-excerpt/

2. basvd
   Member
   Posted 5 months ago #

   The plugin should function despite this error. The easiest thing you can do is turning off (or lowering) error reporting in PHP. Also make sure that WordPress is not in debug mode.

   I will fix this bug in a future update.

3. MattiasP
   Member
   Posted 5 months ago #

   I´ll try that. But the last time I had it on(not sure if debug is on) the whole site stopped working and there were a couple of error messages.

   I´ll get back to you when I´ve tried it again.

   Thanks for the reply!

4. MattiasP
   Member
   Posted 5 months ago #

   It works even though that message is displayed. But now I see two more error messages in settings > excerpt when saving:

   Notice: Undefined index: advancedexcerpt_no_custom in .../wordpress/wp-content/plugins/advanced-excerpt/advanced-excerpt.php on line 262

   Notice: Undefined index: advancedexcerpt_finish_sentence in .../wordpress/wp-content/plugins/advanced-excerpt/advanced-excerpt.php on line 265

   The error messages are not displayed if the boxes are checked in settings > excerpt.

5. MattiasP
   Member
   Posted 5 months ago #

   Now the whole backend goes blank after I press login. And this is one out of six error messages displayed:

   Warning: Cannot modify header information - headers already sent by (output started at .../wordpress/wp-includes/functions.php:3468) in .../wordpress/wp-login.php on line 353

6. basvd
   Member
   Posted 5 months ago #

   This is a common problem with version 4.0 unfortunately. Have you tried redownloading the plugin and manually replacing the files in the plugin directory?

7. basvd
   Member
   Posted 5 months ago #

   Both issues are resolved in 4.1

Reply

You must log in to post.