acesuares

ok

I used the footnote stuff to make something similar, but of course this is not nearly usable code.
1. need to set the dropdown ‘tooltip’ or ‘tooltip and link’.
2. need to use the pro versioon
3. need to set the extra-footer to ‘link’ (if you set to excerpt, something breaks.. ?!??!?!)
4. to be done: figure out how to show these in categories. It just list them all like the footer stuff, but it still shows the tooltip (what we want) AND a list of words at te bottom of the page (shoud also have excerpts).

In /usr/share/wordpress/wp-content/plugins/glossary-by-codeat-premium/frontend/Core/Term_Injector.php at line 109

                    $this->regex_match();
                    $this->replace_with_utf_8();
                        $this->regex_match();
                        $this->replace_with_utf_8();

//Ace
                        $type = new Type\TermsList;
                        $type->initialize();
                        $this->text .= $type->append_content( $this->terms_to_inject );

// end Ace

                        if ( \gt_fs()->is_plan__premium_only( 'professional' ) ) {

So this code is always on, not what you want, but okay for is.

A new file in /usr/share/wordpress/wp-content/plugins/glossary-by-codeat-premium/frontend/Core/Type/ just a copy of Footnote.php, the file named Termslist.php,

with these changes:
class TermsList extends Engine\Base {
*** instead of Footer

public function html( array $atts ) {
return;
// array( 'before' => '', 'value' => $atts[ 'replace' ] . '', 'after' => '' );
}
*** don’t add anything to the word it self (it already has a tooltip and/or link)

/* if ( !\is_type_inject_set_as( 'footnote' ) ) {
return '';
}
*/

*** removed this to make it work

that was it.

So the TermsList thing is always included (which is okay for us but not for others of course) and it makes a list of words (like footnotes) while not touching the tooltips or links. It would be nice to get the excerpts working, and then of course to get the categories working, and that would be great at the end of the page, even better if they could move to the side somehow (maybe with css or so).

I realize this is a mess but I hope you understand what we need and want.

Sorry, I got it, you need to go to settings and enable footnotes.

Hmmmmmm I bought the pro version but enabling footnotes does nothing.
It the docs it says: ‘If your site contains footnotes’… do I need to do something special to have my post contain footnotes? Is there a code or something to make words footnotes? The glossary words don’t turn into footnotes?

Hi Daniele, thanks for the answer! So, if I understand right, footnote mode does only show the words found in the post. I will look at that and then get back to you.

The idea is to have two or more widgets (let’s call them widgets) on the page, that ONLY show the terms that are in this specific posts.

So it the post was this, and the Bold words where in category A and the Italic words are in catergory B:

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi ac lacus fermentum, mollis ex sed, bibendum felis. Pellentesque pharetra condimentum justo vitae mollis. Ut id dui fringilla turpis gravida ullamcorper et a quam. Aliquam erat volutpat. Proin ut pellentesque tortor. Curabitur dictum viverra gravida. In faucibus diam ut mi sodales, vel lobortis dolor dapibus.

Then the page would display the post, with those words tooltipped, as glossary already does, but somewhere else on the page would be two block like this:

Cat A
ipsum – Nunc sit amet turpis rutrum, pulvinar eros.
Morbi – Nullam at tellus at tortor imperdiet pretium.
lacus – Nam scelerisque congue dictum. Duis dapibus ex.

Cat B
consectetur – Praesent id ante ut lectus sodales pulvinar.
fermentum – Aliquam scelerisque malesuada dictum. Pellentesque at ante.

So, to the side of the page you would find ONLY those words that where used in that specific post, with their explanation (the same text as would be shown in the tooltips).

I don’t believe the solution you gave is the right one.
We want this to go ‘automagically’, so once we create the glossary with all the terms divided up in to categories, for every post that contains some words from the glossary, those words would be tooltipped (as glossary does) AND we would want to dispay those words at the side of the page (in a widget maybe).

You’re totally right!
The OneAll Social Plugin manifests itself on the login page, not on the registration page. When someone logs in via a social network, registration happens automagically. So, there is no need for the plugin to show itself on the registration page.
My bad.
It’s working now like it promised ??

Please close the ticket!

You’re totally right!
The OneAll Social Plugin manifests itself on the login page, not on the registration page. When someone logs in via a social network, registration happens automagically. So, there is no need for the plugin to show itself on the registration page.
My bad.
It’s working now like it promised ??

Please close the ticket!

yes, some other theme works.
Our theme is Divi, is that a problem?

needed to flush permalinks!

sorry it seems to work on another domain, probably that one domain has some issues.

I reverted to a backup of the old free plugin and now the third party forms are working again,

After I added a new Pod (custom post type), suddenly those custom taxomonies where gone! Problem solved.

Hi Dsonic, is it showing the username or the common name?
I.e. did you fill in the full name for the person?
Just guessing here, since in our site the name shows up normally.

It’s true.

In line 143 the gmt_offset is subtracted from the birthday timestamp.

if(!is_numeric($userobj->value)) {
$bdate = strtotime($userobj->value) + $this->serveroffset;
}

This is very weird. If the birthday is 6 Mar 2012, the timestamp will be
1330992000. We live in Cura?ao in GMT-4 so the ‘serveroffset’ = -4.

Now 1330992000 – 4 = 1330991996 is March 5, 2012 11:59:56 PM. just 4 SECONDS earlier and thus the wrong date.

Not very clear why the serveroffset needs to be calculated, since a birthday always happens at 00:00:00 (no time is set in the birthday field).

So I just removed the offset for now:

if(!is_numeric($userobj->value)) {
$bdate = strtotime($userobj->value); // + $this->serveroffset;
}