undefined tags

Some other issues.

1) After I save the preference for <fn>, it doesn’t save it in the window and a refresh shows ((, the default used. However, it seems to be using the specified format albeit with the problem described above.

2) I’m not sure why the footnotes are being shown below the author’s biography. These should be showing within the text of the article itself.

3) It’s a great plugin. The option of branding is wonderful and commendable and greatly appreciated. Don’t mind donating. But I think that a choice to use the company name for the plugin in the sidebar makes for great confusion, especially if you have several plugins a site owner may use. Having a dedicated on top of the options is still conspicuous without creating confusion in the sidebar as which company does what, etc.

Great job.

One more thing – table data for the footnotes? In the age of css and using lists, methinks this may be a very outdated, awkward approach that will require css to be added rather than being consistent with typical lists and css for such references. Just some thoughts.

And your products page also has the same problem. Perhaps a conflict with something but it effects the entire plugin. (And the footnote format isn’t saving and now it reverted away from the setting, showing the footnotes styling that is default).

Identity

Website
Version: undefined

Google Keyword Suggest

Website
Version: undefined

competition

Website
Version: undefined

Footnotes

Website
Version: undefined

Hmm… the plugin also adds not one, not two but at least three additional css files to the page download as well, which is not optimal.

I had to rewrite the css files and the display template for the footnotes themselves, which includes inline css (and defeats the point of the css files you’re creating.) Now my footnotes don’t look like tables, which they shouldn’t, and more resemble a list.

In addition, it appears your plugin isn’t designed to save settings in the front end. This is a very, very dangerous problem. If a user saves one setting elsewhere and has a setting other than the default “((” – it will be overwritten and every page with footnotes will lose their formatting.

I’m a little scared to upgrade at this point since doing so would undo all the changes needed to be made above. I hope that you take this constructive criticism in the well natured intent of the poster.

Hi thelaw,

cheers for all the input you’ve given us. It’s sure a hell of a lot to digest in the first place, but we’ll try our best to address each and every issue you’ve brought to our attention.

Let me explain only one for the moment. I’ll have to discuss the rest with my fellow code-warrior Stefan.

The Table format was chosen since users reported abnormal behavior regarding the representation of footnotes in the reference list at the end of a post. Tables have the advantage of calculating column widths in respect to the whole table. I couldn’t find an easy and high-fidelity approach using css. If you have a solution, we’d very much like to hear about it!

Hi thelaw,

wow! Many thanks for your input. I develop / debug a new release version right now and will publish it either today or tomorrow. A few things of your report will be (hopefully) fixed in the new version.

Here is a answer to your report:

I tried using the <fn> tag and got “undefined” inserted into the editor. I could only manually enter it into the visual editor and got it to work. If you add it in the text editor, the tag is removed.
Will be fixed in the new version. <fn> is similar to a HTML tag and WordPress removes it from the editor. The new version will decode the footnote short code in post/pages.

After I save the preference for <fn>, it doesn’t save it in the window and a refresh shows ((, the default used.
Will be fixed in the new version. Same reason as the issue above.

I’m not sure why the footnotes are being shown below the author’s biography. These should be showing within the text of the article itself.
You can change where the reference container appears in the Plugins settings. Available options are: in the footer, at the end of the post, in the widget area (using the Footnotes widget)

But I think that a choice to use the company name for the plugin in the sidebar makes for great confusion…
The reason of the brand is that we have already developed other Plugins in the past and will still develop Plugins in the future. All of our Plugins will appear in this brand to group the settings of all Plugins we have developed. (Currenty the brand is only available in the Footnotes Plugin and will be available in other Plugins in the next days).

One more thing – table data for the footnotes?
Our first versions used DIV elements with CSS attributes. If the Footnote contains a lot of characters the text breaks into multiple lines. This broke the layout of the reference container. So we changed the DIV elements into a TABLE to avoid this issue. If there is enough time we may change the reference container back to DIV elements and solve it with more CSS attributes.

And your products page also has the same problem. Perhaps a conflict with something but it effects the entire plugin.
The new version will contain a fallback value to avoid the 'undefined'. May you post the content of the Diagnostics sub page of the Footnotes Plugin?

Hmm… the plugin also adds not one, not two but at least three additional css files to the page download as well, which is not optimal.
Thats right! The new version has only 2 CSS files. One CSS file for public pages and one CSS file for the settings (will only be loaded when the user clicks opens the Footnotes Settings page). But I also recommend using Optimization Plugins (e.h. Autoptimize) to merge all public CSS files (Theme and other Plugins) to 1 CSS file to increase the performance (page speed).

I had to rewrite the css files and the display template for the footnotes themselves, which includes inline css (and defeats the point of the css files you’re creating.) Now my footnotes don’t look like tables, which they shouldn’t, and more resemble a list.

May you tell us how you changed the tables to improve our Plugins and use it for the other Users too? If so please e-mail me: [email protected].
Would be very nice!

If a user saves one setting elsewhere and has a setting other than the default “((” – it will be overwritten and every page with footnotes will lose their formatting.
In one of the next versions I will also implement a function to overwrite the appearence of all Footnotes in the content of each post/page.

Wow! That was a mouthful, huh?
Jesus. Suddenly everything makes sense!

Please chime in thelaw

Hi thelaw,

have you already tested the new version of our Footnotes Plugin?
Would be happy to get any notification about existing errors and fixed issues.

Hi thelaw,

we hope to have resolved your issues!

I’ll go ahead and close this thread.
If any of the above mentioned points is still open, please open a new thread for each topic. Be it an issue or a feature request.

Thanks for bearing with us.