Hi Peter,

For the first time, I am testing Articles Field on J4 🙂
- "Articles (articles)" seems to work fine so far
- but there seem to be an issue on "Articles - Linked (articleslinked)"

Actually when trying to fill the field "Linked Fields", instead of having a dropdown or something allowing to select the corresponding Custom Field, nothing happens.

So I thought "let's type it manually". I tried typing
- the ID of the wished CF
- the Name of the wished CF

But in both cases (after setting the current CF to "Show" and not "Hide", in the front-end I get the following error message
Probably something you are already aware of, but obviously I'll be happy to test when you have a fix.

[ btw, txs a lot for all you work on the J4 version of your extensions. Very much appreciated ]

Excellent!
That was quick.

The good news: now the "linked fields" option works as expected: one can select the related CF via the interface (actually, it has converted my ID so my intuition of typing the idea was not bad)

The bad news: when publishing the CF, I still get the following error in front-end
Halfway through 🙂

As I was saying: in front-end.
As I was not stating expliciting: just when viewing (not tested front-end edition so far 😁 )
(When editing the article or the Field in the backend, everything looks fine)

oh gosh. I am the happy one discovering an unknow bug then 😁
Let me know if I can help

Wonderful!

It is a really exciting time now that almost all your extensions are (or are about to be) J4 ready 🙂
Keep up the good work.

I am looking forward to Tabs & Accordions in particular.
But first things first. It will come in due time.
The vanilla JS will be a great improvement (I was not able to use Tabs and Sliders for several years bc of BS4 not being compatible anymore with BS2).
So your extensions will become universal. Yeah!

Site still working fine after the update. Phew ! 😁
Txs

oh, just one thing worth to mention: after your direct intervention on the site (and before making the latest update 1 minute ago), when Saving one of the CF I had an error message about "a primary key" (?).
I hope it is just a false alarm and that no side-effect will come of it

It just happened once, the first time I saved a CF after you did something to fix.
So I keep my fingers crossed that it will not happen again and that the database is not tweaked 😁