Interesting, but some issues

  • Resolved KTS915

    (@kts915)


    9 years, 4 months ago

    This looks very interesting.

    Unfortunately, when I install it (running PHP 5.5, and testing on a localhost development site), I get the following message:

    The plugin generated 1616 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.

    Then (with debug on), I get the following messages once the plugin is activated:

    Strict Standards: Declaration of Indexy_Glossary_Index_Widget::widget() should be compatible with WP_Widget::widget($args, $instance) in ~/wp-content/plugins/indexy/classes/Indexy_Glossary_Index_Widget.php on line 31

Strict Standards: Declaration of Indexy_Glossary_Index_Widget::update() should be compatible with WP_Widget::update($new_instance, $old_instance) in ~/wp-content/plugins/indexy/classes/Indexy_Glossary_Index_Widget.php on line 31

Strict Standards: Declaration of Indexy_Glossary_Index_Widget::form() should be compatible with WP_Widget::form($instance) in ~/wp-content/plugins/indexy/classes/Indexy_Glossary_Index_Widget.php on line 31

Strict Standards: Declaration of Indexy_Related_Posts_Widget::widget() should be compatible with WP_Widget::widget($args, $instance) in ~/wp-content/plugins/indexy/classes/Indexy_Related_Posts_Widget.php on line 31

Strict Standards: Declaration of Indexy_Related_Posts_Widget::update() should be compatible with WP_Widget::update($new_instance, $old_instance) in ~/wp-content/plugins/indexy/classes/Indexy_Related_Posts_Widget.php on line 31

Strict Standards: Declaration of Indexy_Related_Posts_Widget::form() should be compatible with WP_Widget::form($instance) in ~/wp-content/plugins/indexy/classes/Indexy_Related_Posts_Widget.php on line 31

    Pages also now take an age to load, which was not the case before.

    https://www.ads-software.com/plugins/indexy/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author MrBunnyFlop

    (@mrbunnyflop)

    KTS915, thank you for bringing this issue to my attention. I’ll push out an update fixing this problem soon.

    Depending on how many glossary articles are created, the amount of work the plugin needs to do for each post increases, however there shouldn’t be a noticable slowdown. I do have some improvements planned to speed up particularly installations with many articles.

    Thread Starter KTS915

    (@kts915)

    Thank you. I look forward to testing out the update.

    why don’t highlight the terms when are in custom fields?

    how can i do it?

    Thanks in advance.

    Plugin Author MrBunnyFlop

    (@mrbunnyflop)

    bunbury, since I cannot predict what custom fields may exist in any given WordPress setup, and what they are used for, currently Indexy doesn’t highlight data in custom fields by default.

    However, if you are not afraid of diving into the code, inserting a simple add_filter() call may be all you need to get it to highlight custom fields (or anything else, for that matter). All it takes for Indexy to highlight post content is the following line:

    add_filter( ‘the_content’, array( ‘Indexy’, ‘highlight_post’ ) );

    Alternatively, in your theme, you can wrap anything you want highlighted in a call to the same function:

    echo Indexy::highlight_post(“whatever you want to be highlighted”);

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Interesting, but some issues’ is closed to new replies.