mdn_count

etc · 2016-09-30 10:43:14

Makes me think that <txp:article_custom /> could accept pgonly attribute (without setting the pagination stuff) and return just the number of pages in this case. Yay, nay?

Dragondz · 2016-11-16 09:36:18

Hi

After upgrading to txp 4.6.2 i got this error :

Erreur de balise : <txp:mdn_count section="site" category='<txp:category />'/> ->  Textpattern Error: Unknown column 'NULLDATETIME' in 'where clause' lors du traitement du module “Aucun” dans le gabarit “2016”

What s NULLDATETIME, i havent found anything even on google!

it refere to this line 46 :

$q[] = $andor.' (Posted <= now() and (now() <= Expires or Expires = '.NULLDATETIME.'))';

NULLDATETIME is not a mysql constant, then maybe a txp constant ? but i found nothing about it ?

UPDATE : it seems that the constant was defined on constants.php on txp 4.5.7 and before, but the constant is nt in new version,
I added

define('NULLDATETIME', '\'0000-00-00 00:00:00\'');

to the plugin and the error vanished.

Last edited by Dragondz (2016-11-16 09:58:44)

NicolasGraph · 2016-11-16 09:56:09

Dragondz wrote #302935:

What s NULLDATETIME, i havent found anything even on google!

You can find some info on the forum using the search engine.
Does this help in your case?

Dragondz · 2016-11-16 09:59:28

Merci Nicolas

To make mdn_count work i had to change line 46 like this:

$q[] = $andor.' (Posted <= now() and (now() <= Expires or Expires is null))';

Bloke · 2016-11-16 11:02:45

Dragondz wrote #302935:

Unknown column ‘NULLDATETIME’

Here’s the plugin fix from a post the other day.

I added define('NULLDATETIME', '\'0000-00-00 00:00:00\'');... to the plugin and the error vanished.

Not advisable. The reason it was removed is because MySQL and its various forks are starting to remove support for zero dates. Results are undefined if you use them and vary from version to version. If you feel you must use it, this is better:

define('NULLDATETIME', '\'1970-01-01 12:00:00\'');

But changing the code as you’ve done to use IS NULL is far better.

Dragondz · 2016-11-16 12:02:20

Thanks Stef.

jayrope · Yesterday 20:04:14

Since updating to 4.9 sthg like

<txp:custom_field name="band_name" /> (<txp:mdn_count customfield="band_name" customvalue='<txp:custom_field name="band_name" />' />)

supposed to count the number of entries in a particular custom field does not display the result anymore.
Anyone aware of this?
I’d be happy to get rid of mdn_count altogether otehrwise, but haven’t a new way of counting those entries.

Thanks for any pointers.

Last edited by jayrope (Yesterday 20:13:04)

jakob · Yesterday 20:29:45

jayrope wrote #342489:

I’d be happy to get rid of mdn_count altogether otehrwise, but haven’t a new way of counting those entries. Thanks for any pointers.

That should be possible. Oleg gave a pointer a few posts up and here’s an example of that in use.

This is the Textpattern welcome article. You can delete or edit it and then start creating your own content.

Textpattern in two minutes provides an overview of Textpattern. Textpattern user documentation provides more detailed information.

For example, if you have a list of articles with song titles and a custom_field band_name, this will return your article counts:

The Beatles: <txp:article_custom band_name="The Beatles" pageby="1" pgonly />
Rolling Stones: <txp:article_custom band_name="Rolling Stones" pageby="1" pgonly />

You can get a comma-separated list of your band names using

<txp:article_custom break="," sort="custom_1 desc" variable="all_band_names" trim>
<txp:if_different><txp:custom_field name="band_name" /></txp:if_different>
</txp:article_custom>

(assuming band_name = custom_1)

From that you could build an automated list…

jayrope · Yesterday 22:07:22

Hey Jakob, Du bist immer so am Start, herzlich Dankeschön!

I can’t quite see somehow, how your example would just return a number, the actual count of articles using a particular custom field entry…
I am using my above script in an article body, in between text. Can you elaborate?

Last edited by jayrope (Yesterday 22:07:42)

jakob · Yesterday 22:21:05

jayrope wrote #342491:

I can’t quite see how your example would just return a number, the actual count of articles … Can you elaborate?

Have a look at the two attributes in the article_custom docs:

pgonly outputs the number of pages (of results) as a number, and
setting pageby="1" means you would be paging by every article instead of the default 10 per page.

The result is the number of matching results. The credit should go to Oleg, though.

jayrope · Yesterday 22:34:03

jakob wrote #342493:

Have a look at the two attributes in the article_custom docs:

pgonly outputs the number of pages (of results) as a number, and

setting pageby="1" means you would be paging by every article instead of the default 10 per page.

The result is the number of matching results. The credit should go to Oleg, though.

I’ll try, thanks a lot. I always thought, that I should not use an article tag inside an article body. I’ll report back

jayrope · Yesterday 23:49:28

jakob wrote #342493:

Have a look at the two attributes in the article_custom docs:

pgonly outputs the number of pages (of results) as a number, and

setting pageby="1" means you would be paging by every article instead of the default 10 per page.

The result is the number of matching results. The credit should go to Oleg, though.

This has worked, thanks a lot! So i got rid of mdn_count finalmente.

I found a bug, though. Using

<txp:article_custom band_name="<txp:custom_field name="band_name" />" pageby="1" pgonly />

with an entry in the custom field containing an “&” (an ampersand) does not count that entry and
reports a count of zero, instead of counting and reporting the respective entry as 1.
You can see the live example on https://www.kliklak.net/live-dates/past-concerts-by-artist

Namely the custom field called “band_name” containing “jayrope & Ansgar Wilken” counts zero, whereas “jayrope + Ansgar Wilken” using a “+” sign instead of an ampersand counts 1 per entry. Oopsie :)

Very small bug, is that a 4.9 issue? I am wondering where to report this.

Last edited by jayrope (Yesterday 23:53:14)

Bloke · Today 00:22:15

Try single quotes when you use tags-in-attributes so the content is parsed :)

<txp:article_custom band_name='<txp:custom_field name="band_name" />' pageby="1" pgonly />

If that still doesn’t work, we’ll go from there and investigate reasons.

Textpattern CMS

Textpattern CMS support forum

#106 2016-09-30 10:43:14

Re: mdn_count

#107 2016-11-16 09:36:18

Re: mdn_count

#108 2016-11-16 09:56:09

Re: mdn_count

Dragondz wrote #302935:

#109 2016-11-16 09:59:28

Re: mdn_count

#110 2016-11-16 11:02:45

Re: mdn_count

Dragondz wrote #302935:

#111 2016-11-16 12:02:20

Re: mdn_count

#112 Yesterday 20:04:14

Re: mdn_count

#113 Yesterday 20:29:45

Re: mdn_count

jayrope wrote #342489:

#114 Yesterday 22:07:22

Re: mdn_count

#115 Yesterday 22:21:05

Re: mdn_count

jayrope wrote #342491:

#116 Yesterday 22:34:03

Re: mdn_count

jakob wrote #342493:

#117 Yesterday 23:49:28

Re: mdn_count

jakob wrote #342493:

#118 Today 00:22:15

Re: mdn_count

Board footer