tvejacques

Michael Beckwith
It must be the drop-down then. But there are other tools that use UI presentation in similar format to WP Pages/Posts windows – which are also easier to navigate than the drop-down.
So it is a UI limitation. Our test site has 700+ categories, without a problem. Computerized systems in the 1980s used 1000+ Dewey classifications.
Pity then, as your plugin is great for many functions. You are forcing us now to look elsewhere.
Or is there perhaps not a quick fix to disable the drop-down, and play out the taxonomy data in a different format?

James Huff – thanks for replying.
Done all that in the first round with Toolset.
Even began over with a clean WP.
Even with all (but standard security plugins) deactivated, on a clean installation, this happens. No other development yet.
If the same thing happens with a different plugin on the same functionality, either both plugins have independently the same code problem, or there must be something in WP that cause both to do the same thing. Really strange that both give exactly the same problem, more or less at the same added data amount.
Could there be a default memory limit on taxonomy that needs to be increased?

Oops… it should not say permalink, but slugs.

It can’t be a cookie problem. It happens on my box, and on the box of someone on a different continent.
I have the same problem as andytwonames – the dashboard menu does not want to expand. BUT I also have some annoying menu that popped up and does not go away. That menu seems to be a list of categories we were busy adding.
See screenshot at https://www.care4tulbagh.org.za/annoying2.png

bcworkz thanks again.

James Huff
Alt + Print Scr works on my Ubuntu box, but does not paste here.
So I put the screenshot here (Page/Post duplicates marked): https://www.care4tulbagh.org.za/export-duplications.png

bcworkz Must be plugins. The instances further down the list do not show the pop-up for more options.

You have been very kind and patient to assist us, bcworkz! Thanks so much.

Given the various problems (still unsolved) we experience, it is probably best to start again. Something must have gone wrong during the export/import process from the Dev site (where the basic skeleton was developed) to the final site. Fortunately we are not far down the development path on the final site, building on top of the skeleton.

Question (hopefully last on this topic):

If we purge the slug table (to get rid of duplicate slugs), can we then add slugs to the pages – without breaking the system completely? This is after all not yet a working site.
Fortunately we keep a separate record of the slugs and permalinks off site, so updating a clean table will be much quicker than to redo everything form the start.
PS: the JetMenu support have been unsuccessful for a far too long time to find a solution – perhaps that battle is also due to gremlins that arose from the export/import process.

Hi bcworkz
Thanks for all your help thus far.
I found the problem, but have no idea why it happens.
It is the Menu.
We tried a couple of menu plugins, and the culprit is JetMenu.
When using their menu plugin, somehow the links go through some script (I think) as it calls up product page templates. That despite in their location settings that Pages was selected.
Other menu plugins (e.g. Essential Blocks), using the exact same settings, link to the correct target pages.
Problem thus solved, but I’d like to understand Why?

Thanks again for your great support
Keep well

Thanks bcworkz
These are static Pages that will form the structural backbone for reference purpose.
The dynamic pages will interact with those static pages.

So presently there is no queries or scripts other than very basic page rendering.

On the Dev and Test site, it works perfectly.
Given the present delay, we might just re-import from the test site – it does indeed seem some gremlins slipped in during the export/import process.

Thanks bcworkz

I have indeed tried those places but after saving a “this-word”, the refreshing window reverts back to “this-word-2”. It refuses to remove the -2.

bcworkz I appreciate your feedback (this post and the others you have assisted me with). You are good people.

I am still trying to find the problem

bcworkz thanks a million!

Thanks bcworkz

I did suspect “initial this-word resource was removed” as the problem. During import from the development-site we had server problems as well as network problems – and at that time I was wondering whether we would encounter problems.

What I did expect from WP (first time we use this platform) is that the data of the slug would exist somewhere in a format that could be editable – such as a DB field. Pity one cannot do this – especially as we’re still in early stage of development, which means we will sit with this dirty little thing forever ?? — I like consistency and neatness.

If I understand you well, slugs are primary, and need to be overridden with permalinks to enforce a different URL structure.
Ciao
jq

Thanks bcworkz
I think I had it the wrong way round if slug comes first (as I understand you), and then permalink. I thought one starts off with the preferred custom permalink that overrides the automatically created slug.
But if the custom permalink differs from the automatic slug, which is used in links? Does the custom permalink override the slug?
Example:
* Custom permalink: this-word
* WP created slug: this-word-2
Which is used for the link, and which will show in the public display of the page/post?