tvejacques

Thank bcworkz

I indeed usually do the deactivation on the primary site when troubleshooting.
Will do the manual “update” thing – thanks for that link.
I am really disappointed with WordPress. The moment one does something more than a blog, brochureware or basic shop – something with a mix of more functionalities – plugin conflicts are severe and we waste an unbelievable amount of time.

You have been a great help on several other problems we’ve experienced – thanks so much for that.
_______
PS

We do a bit of development and everything works fine, then when trying to add another functionality provided by another plugin, problems start. On occasions we have tried 10+ alternative plugins for the same general purpose, and as they all give some or other problem (not always the same effect, though), we have to go back only to find the culprit is some other implemented plugin with a totally unrelated functionality.

We then need to find a replacement for that plugin, thus redesigning what was already done and waste days on end. For example, we’d use a block plugin to build template parts, then do lots of other stuff, only to discover it is the bad boy, redo all those templates, and redo everything else that sits on top of that.

We’ve had to chuck expensive themes, we tried various block builders, menu plugins, taxonomies, media management, conditionals, vendor management, and a very long list of others.

Plugins for the same broad purposes offer different features. Clashes might occur because a particular feature of another plugin of a different “family” of purpose clashes with one from another “family”.
Plugins should have the ability to have some of their features disabled – being object oriented that should not cause problems.

WordPress should have stricter guidelines for plugin developers.

I tell this long story because if we knew beforehand what we know now, we would have just rather have developed everything on a programming platform. I did mention somewhere that 20 years ago we developed a solution in PHP with more complexity than our present project. That went smoothly. We thought WP would be quicker.

Thanks for your support

??

Thanks bcworkz
Found the culprit.
It was “Conditional Logic for Woo Product Add-Ons”

Much appreciated threadi

Yes, your summary is something of what we’re looking for. But not totally. We are trying to avoid trips to the server, which is why we can’t use the “standard” WP function – the one you explained.
On the theme: we use the default 2024 theme, but build our own patterns and template parts, thus not really using the theme except to serve as some kind of foundation in order to avoid getting too deep into coding.
Due to all the plugin problems we have experienced, we halted further development. We were two month down the line when some really big problems began – due to conflicts. We will need to rebuild some basic foundations. Now we’re focusing on testing plugins, building small testers to avoid problems down the line again.
So for now we are satisfied with your response and we can close this.
BTW: our proof-of-concept site (using pseudo-code) was not done in WordPress. We need to translate that into the WP environment – but as the saying goes: things get lost in translation ??
Thanks again for your time and effort trying to help us.

Your responses are appreciated, threadi

1. The following is easy to do in WP for the frontend:
   * Some information is displayed on the public user side frontend
   * Click + sign and more info appears.
   This happens without requiring a request from the server to add.
2. Now extend that feature to this:
   * When clicking the + sign, a block is duplicated on the user side, without a trip back to the server. It is not in the “package” of the first page request. It is created during the session and added on the fly (so to speak). There must be JavaScript to do that.

Is #2 possible?
* What is the WordPress lingo/terminology for this type of function?
* Will some kind of plugin be needed to do this? What type? We have not come across how this might be handled in any of the documents of block building plugins.

The second part then:

If that block creation as in #2 is possible, and the block created on user side contains form data, we’re just wondering if there might not be confusion.
Here is the input box: it contains the ID of the database field into which the data must be added.
Now if it is possible to have that block created user-side that contains another input box, to send the data to the correct table field, that second block will contain the same ID as the first block.
So two data strings with the same field ID will be send in the same session.

Will WP handle this properly? Will WP add the first string first and the second one secondly without having to building the necessary code-level measures?
Our confusion about this is because we do not know the structural architecture of WP’s table constructions and relations. But if we need to get into such technical details, it is often easier to build one’s own tables than to try to understand tables designed by others.

Our project can use table designs from a project of 20 years ago, but then we would loose functionalities provided by WordPress.

Thanks threadi
We do understand that the basic WP installation cannot handle this and would require a form plugin.

It seems that my post heading is a poor one. Our basic question is more about user-side element creation, and then following on that the question related to forms.

There seems to be two aspects of importance for our case:
* The ability to create a block (or perhaps rather element within the block) on user side and reveal that for various purposes when needed – but without a trip to the server. With this reveal we do not mean with the basic conditional method to hide and reveal, but rather the creation of a new instance on user side. As the same type of function will be used for many other use cases, we’re looking for such a method – which is why we posted the question here in WordPress Support. So we’re looking for something that can “build” something on user side, and were wondering if there is a basic WP method to do this.

* For data input a form plugin will certainly be required.
Our form-related question is whether in cases where a block/element is created on user side for the same field, will the basic functionality of a form plugins pass the input data correctly to the data table? – as there will be more than one data inputs on the same field on the same page on the same trip to the DB server.
Will the automatically installed set of data tables of the WP install handle this without tinkering?. Or would we need to tinker with the DB – such as creating additional tables with foreign keys?

We haven’t yet decided which form plugin to use. We still need to research and review. Any suggestions?

Our experience with WP plugins has been (surprisingly) very poor. We’ve had to trash more than 10 plugins thus far that we bought for different functions due to conflicts with other plugins – typically with basic block building plugins (of which we tried several ones too). That despite we tried “best voted” plugins. We do some development, then a conflict arises; then troubleshooting; then trashing the culprit, and start again. And when we need to trash the block plugin, then we need to re-develop those bits. Lots of time wasted. (I won’t get into naming culprits here).

We’ve wasted a frustrating lot of time troubleshooting conflicts. In this regards we’re sorry we tried the WordPress solution – we thought it would save time. It would have been much quicker to start our development from scratch with PHP.
It seems that WP is great for typical installations (such as brochureware and shopping), but the moment one wants to do something out of the norm, diving into coding is better.

Thanks for replying threadi

What I described is on the user side, when entering his information. We need to allow for several phone numbers for the same user (separately), and do not want to clutter the UI. So to start with we display only one input box for the phone number.

We’ve done this successfully in the past (not with WP). The user enter his phone number, and if he wants to add another phone number, he clicks “Add another number”, and a new instance of the same input box is added to the UI (without submitting the form). This process can theoretically continue ad infinitum.
We know how to do this with PHP, table designs, and necessary front-end scripts.
So my question really is, is there a WP shortcut to do his, or must we delve into the engine room to do this?

Thanks.

The only two tables with string blogs are
* _blogmeta
* _blogs
without the digits _2 or _3
thus probably that of the primary site.

Jose Castaneda
No luck.
I went through the table list a few times.
Of the 531 tables listed, not a single one contains the strings “wp_blogs”. In fact, only 5 start with the string “wp”.
https://www.care4tulbagh.org.za/tables1.png
My service host says this is a question they cannot answer, and I must get the answer here.
I also went through found the php files to see if I could find something. network.php looks like the instruction set, but of course won’t include the mapping info.

Aaah Jose Castaneda – thank you so very much.
I’ve been searching for an answer for more than two weeks, and none of the support people on many sistes seem to know the answer.
Fantastic.
I will have a look.
Have a great day!

Michael Beckwith thanks for your reply.

Each of those actually have child classes. Think more along the lines of a library or encyclopedia. There are lost of top level classes and many more sub-classes. What appears to be flat is just the high-order level. So if, for example, the present 800+ high-order classes are grouped into 4 primary classes, each will have 200 on the 2nd level, which means there will be 796 second-order ones, still resulting in the UI problem.

There are many large taxonomies in the world. Medical, for example. And there are 249 different bird families with 2,057 genus and 11’000 species.

The problem is the drop-down interface showing the list of taxonomy items. The drop down does not have the capacity for large numbers. A different type of interface is required. Instead of a drop-down a list such as on Page/Post pages would solve this problem.
Been in contact with plugin guys. They say they use WP UI, so it is not their problem.
BTW, other plugins we tested that use a different UI can handle 800 items without problem.

…
if the drop-down could be arranged with first level letters from the alphabet, and then second level lists the array by first letter:
A –> Alpha
etc
B –> Beta
etc