updating 4.4.1 > 4.6.2

bici · 2018-04-18 03:25:16

oh ? .. removing the ID ref. worked much better. But it output the wrong sticky entry. One that was for the Clients list. So i have Article D 2 which is for the Home page. and Article ID 3 for the Clients section. How to select the appropriate article to output? both are sticky status

…so close

bici · 2018-04-18 03:40:02

so. now i have the sticky article on my Clients Page/Section . The last issues is that the same sticky article is appearing on the home page. instaed of the other sticky article meant for the home page.
…sooooo close

bici · 2018-04-18 03:46:27

WOOT! UPDATE I solved this last issue by using offset=“1”

now on the sections that are working i get an error along the the lines of:

Tag error: <txp:upm_article_image form=“article_image_form” wraptag=“ul”
any clues of why? The page works otherwise.

phiw13 · 2018-04-18 04:15:50

bici wrote #311159:

WOOT! UPDATE I solved this last issue by using offset=“1”

That is one option. I would have suggested using <txp:article_custom />, which does have an ID attribute.

Dunno about your other issue. What is the actual error?

bici · 2018-04-18 04:22:43

they seem to be related to :

 Tag error: <txp:upm_article_image form="article_image_form" wraptag="ul"
class="thumbs noscript" /> ->  Textpattern Notice: unregistered_tag while parsing form gallery on page master

phiw13 · 2018-04-18 05:19:06

A classic :-)

Lots of forum entries on that one: like this or this one.

bici · 2018-04-19 04:32:29

phiw13 wrote #311163:

A classic :-)

Lots of forum entries on that one: like this or this one.

phiw13, many thanks for all your help!

as for trying to fix the upm_image Plugin —- that seems rather daunting for me to tackle. I really don’t understand what i have to do.

I am wondering if these plugin updates will be farmed out to volunteers who can easily update these plugins… or so i hope!

jakob · 2018-04-19 04:57:04

bici wrote #311159:

WOOT! UPDATE I solved this last issue by using offset=“1”

That was probably a sort order thing. Sometimes it’s enough to amend the date of the article to be more recent (if the list is being sorted by the default posted desc), so your preferred article shows before the other one. Philippe’s solution with article_custom id="123" is more robust because it doesn’t depend on things like sort order or published date which can change, but it’s also less portable as it is specific to that site’s setup and its article id numbers.

bici wrote #311201:

as for trying to fix the upm_image Plugin —- that seems rather daunting for me to tackle. I really don’t understand what i have to do.

As of txp 4.6. (or thereabouts) a registry of permitted tags was introduced to reduce the risk of exploits. Plugins should register any new tags they add to the registry. At some point in the future tags not in the registry will be disallowed.
In 4.6.2 (and I believe in 4.7 too), it’s not mandatory, so the plugin will still work but displays a notice as a reminder. The notice doesn’t show in “Live” mode. The changes Philippe linked to add the tag names to the registry and the notice then disappears in “debug” or “testing” mode too.

bici wrote #311201:

I am wondering if these plugin updates will be farmed out to volunteers who can easily update these plugins… or so i hope!

I’ve done that for a few (in my view) really vital plugins but it’s not worth it for upm_image. As far as I remember, everything you did with upm_image can now be done with txp:images and txp:image so you just need to amend your code and can remove the plugin.

bici · 2018-04-19 05:02:26

jakob wrote #311203:

That was probably a sort order thing. Sometimes it’s enough to amend the date of the article to be more recent (if the list is being sorted by the default posted desc), so your preferred article shows before the other one.

hmm. it would be nice to have a way to make each artilce appear in its proper place as they may be edited and the potentially be displayed in the wrong order?

I’ve done that for a few (in my view) really vital plugins but it’s not worth it for upm_image. As far as I remember, everything you did with upm_image can now be done with txp:images and txp:image so you just need to amend your code and can remove the plugin.

As of txp 4.6. (or thereabouts) a registry of permitted tags was introduced to reduce the risk of exploits. Plugins should register any new tags they add to the registry. At some point in the future tags not in the registry will be disallowed.
In 4.6.2 (and I believe in 4.7 too), it’s not mandatory, so the plugin will still work but displays a notice as a reminder. The notice doesn’t show in “Live” mode. The changes Philippe linked to add the tag names to the registry and the notice then disappears in “debug” or “testing” mode too.

ok. we can look at dropping the use of upm_image sometimes soon. in the meantime the warnings, that are not shown in live mode we can live with.

updated for spelling

Last edited by bici (2018-04-19 05:03:38)

bici · 2018-04-20 00:46:19

jakob wrote #311203:

As far as I remember, everything you did with upm_image can now be done with txp:images and txp:image so you just need to amend your code and can remove the plugin.

ok. this is current code for images :

 <h2><txp:title /></h2>
<txp:upm_article_image form="article_image_form" wraptag="ul"
class="thumbs noscript" />

so would be replace the 2nd line with txp:images and txp:image

and here as well:

 <li><a href="<txp:upm_img_full_url />" title="<txp:upm_img_caption />" class="thumb" >
<img src="<txp:upm_img_thumb_url />" alt="<txp:upm_img_alt />" /></a>

sorry for my thickness on this

phiw13 · 2018-04-20 02:42:02

Take some time to review the user docs? For the first one (documentation), maybe something like:

<txp:images form="article_image_form" wraptag="ul" …

For the second one, the <txp:image_info /> has a wealth of options (documentation). See also <txp:image_url /> (here) and <txp:thumbnail />.

Textpattern CMS

Textpattern CMS support forum

#25 2018-04-18 03:25:16

Re: updating 4.4.1 > 4.6.2

#26 2018-04-18 03:40:02

Re: updating 4.4.1 > 4.6.2

#27 2018-04-18 03:46:27

Re: updating 4.4.1 > 4.6.2

#28 2018-04-18 04:15:50

Re: updating 4.4.1 > 4.6.2

bici wrote #311159:

#29 2018-04-18 04:22:43

Re: updating 4.4.1 > 4.6.2

#30 2018-04-18 05:19:06

Re: updating 4.4.1 > 4.6.2

#31 2018-04-19 04:32:29

Re: updating 4.4.1 > 4.6.2

phiw13 wrote #311163:

#32 2018-04-19 04:57:04

Re: updating 4.4.1 > 4.6.2

bici wrote #311159:

bici wrote #311201:

bici wrote #311201:

#33 2018-04-19 05:02:26

Re: updating 4.4.1 > 4.6.2

jakob wrote #311203:

#34 2018-04-20 00:46:19

Re: updating 4.4.1 > 4.6.2

jakob wrote #311203:

#35 2018-04-20 02:42:02

Re: updating 4.4.1 > 4.6.2

Board footer