ecdltf

You said it mainly checks for bots. So what’s the difference between the 3 levels?

If I set it to High, are there chances that it will block a normal web browser?

What do mean approximatively with “user behavior”?

I deleted the cache and the code is on the page now. A test comment has passed through.

Maybe you should mention it somewhere that we have to delete the cache to make the Antispam work ??

Thanks for the efforts.

Tom

In case it helps, these are the currently active Jetpack plugins:

Enhanced Distribution, Extra Sidebar Widgets, Monitor, Notifications, Omnisearch, Publicize, Related Posts, Sharing, Shortcode Embeds, Site Verification, Spelling and Grammar, Subscriptions, Widget Visibility

Nope.

This is the site: https://dflect.net

Ninja’s Antispam (comment) is active and set to Low.
Akismet is active. But think this is not related.

The number was always #1.

I’m using the default WP comments, no custom forms; and no plugin that affects comments, as far as I can tell. Jetpack Comments are not activated.

That’s funny. At the time after my initial post above, I also stumbled upon the missing ‘else’ at line 332. I “fixed” it, but – as I’ve seen now – slightly the wrong way ?? and so I’ve quit my efforts to make GHPSeo work.

Thanks, JessStryker, for chiming in. So, at the end making this thread was not as useless as it seemed to me. Maybe I’ll try it a second time with GHPSeo in the future.

Cheers

Tom

Would be great if you could make the usage of the shortcode optional. As mentioned, in my hack it is obligatory. It would be better like this:

1. If the shortcode is present the footnotes will be placed there
2. If no shortcode is in the body the footnotes will be placed according to the priority set in line 43

This way we could work without shortcode for the bulk of normal pages, and place the shortcode only when necessary, for the more special pages.

By the way: Why not making the priority setting accessible via the GUI? As we’ve seen this already gives quite some flexibility if you have elements from other plugins in the bottom zone of the article (18 for the Share buttons, 20 for the Related Posts, …)

Thanks for the very nice plugin!

Tom

ok, thanks. I already thought there was something with my eyes ??

can’t seem to get your suggested shortcode to work… any tips?

It’s simple, because the function is already there, you just have to add the shortcode:

1. Open the file easy-footnotes.php which is in the directory /wp-content/plugins/easy-footnotes/. (Open it with a text editor, for example TextMate or TextWrangler, or Notepad++ if you’re on Windows; do not open it with MS-Word or such.)
2. Comment the line add_filter('the_content', array($this, 'easy_footnote_after_content'), 20); which is around line 43. A valid comment prefix is//
3. After the commented line add the line add_shortcode( 'placenotes', array($this, 'easy_footnote_after_content') ); where placenotes is the desired name of the shortcode.
4. Save the file easy-footnotes.php
5. Add the shortcode in your articles to make the footnotes appear there. (Reload page, empty cache if necessary.)

It doesn’t matter which name you choose for the shortcode, as long as it is not reserved.

However, in case the author of the plugin is already working on an implementation of the feature, it would be nice if he would tell us how his future shortcode will be named, so we won’t have to edit our articles again;-)

Please note that when you make the changes as described above you have to place your shortcode in the article, otherwise the footnotes will not be visible. (i.e. placing the shortcode is not optional; an optional shortcode requires some more changes.)

If you only want to change the placement of the footnotes relative to some other elements which are placed by other plugins, it is sufficient to change the priority in line 43. For example, as mentioned in the post above, set it to 18 if you want the footnotes to appear above Jetpack’s Share buttons.

When a developer removes previously well working features, this normally means that he is thinning out the code in order to maintain compatibility with the current WordPress, without actually updating the code.

This, in turn, could mean that the status of the plugin has changed from “actively developed” to “maintained”, or even “abandoned”. Also the fact that the author hasn’t commented on this 2-months-old thread points in that direction.

So, has anybody used/tried similar plugins? Which one is recommendable?

For me it works perfectly now. It’s also cool that a second tap takes me to the “real” footnote.

Thanks for the fix!

Side note: I’m still working on setting up a shortcode to place the notes in a template as well.

That’s great news to hear.

However I have to admit that, since the placement problems with the jetpack elements are solved, I’m currently no longer using my placenotes shortcode. (I’ve also reduced the number of my custom next-post links.)

But in any case, an optional placenotes will greatly augment the flexibility of EF and make it usable for every kind of page structure.

I also switched the priority so it will show above the Jetpack related posts. I’d been meaning to do that, but my site has had an issue with Jetpack’s related posts and stopped showing so I forgot about it.

I’ve noticed that a priority of 20 is fine for the Related Posts links, but still too less for Jetpack’s Sharing buttons (Twitter, Mail, etc.). They get inbetween.

I’ve set it to 18, but it seems that anything between 11 and 19 is OK.

I can confirm this. It’s very clumsy on the iPad.

Sometimes I manage to get rid of the box by tapping outside, maybe 1 out of 10 taps (and tapping around like nuts ;-).

Thanks for having considered my proposals.

what are you using for your next and previous links?

ATM these are just divs with some associated CSS, entered via shortcode. That means, even with a priority of 20 for easyfootnotes, they will always be between the text body and easyfootnotes. But probably I could add these links also via content filter and custom priority?– in the future (I’m just starting to learn WP/PHP…).

But there are other “complications” regarding the placement: I have some more standardized footer elements, a “Sources, Credits, More Info” and sometimes a “Changes” (change notes for scripts, apps). The best footnote position depends on the length of these elements and of the footnotes. For example if there are 30 lines of change notes and a single line of footnotes, it’s more appropriate to place the footnotes before the change notes, and viceversa (from a reading-pragmatic perspective; personal opinion).

That’s why I think that the described “[placenotes]”-type shortcode is the ideal solution to guarantee some flexibility. As already mentioned, this could be a completely “silent” option, that is, in absence of the shortcode the footnotes will be placed simply at the end. So, the “non-technical” user won’t get bothered by additional settings challenges.

[There are some other things that make it impossible (for me) to use the plugin right “out of the box”, without modifications. But since this is not directly related to the placement question I think I’ll better open another thread.]