Estasoft Name Catalog

[wpned_search] – live search box with gender and origin filters (AJAX, no page reload). Matches a name’s meaning as well as its title (searching “sun” finds a name meaning “sun, day” even if it isn’t spelled that way). Attributes: target (CSS selector of a results container to update instead of its own – used to combine with an existing listing so there is only ever one results area on the page), fixed_gender / fixed_origin (lock the query to one taxonomy term and hide that dropdown – handy on a page that’s already about one gender/origin), columns (1-6, default 3). [wpned_az] – A-Z browsing…

Every database query goes through WP_Query or a fully prepared statement – no raw, unescaped SQL. All admin form submissions and AJAX requests are nonce-verified and capability-checked. All output is escaped at the point of output; JSON-LD output is additionally hardened against a literal in any field breaking out of the schema block. The Compare Names and Sibling Generator tools build their UI from raw JSON field values entirely through safe DOM methods (never innerHTML of untrusted text), so a name or meaning containing markup can never execute as code. Uploaded import files are stored…

The Gender taxonomy ships with “Boy” and “Girl” by default. You can rename or add terms under Estasoft Name Catalog > Gender at any time, since it’s a standard WordPress taxonomy – and any new gender value in an imported file is created automatically.

Yes. Add a single-wpned_name.php, archive-wpned_name.php, or taxonomy-wpned_gender.php / taxonomy-wpned_origin.php file to your active theme and it will automatically override the plugin’s default template.

Create a new Page (e.g. titled “My Namelist”), add the [wpned_favorites] shortcode to it, publish it, then go to Appearance > Menus in wp-admin and add that Page to your navigation menu like any other page. No extra plugin configuration is needed – favorites are stored in each visitor’s own browser, so the page just displays whatever they’ve saved.

No. This plugin detects whether one of those is active and lets it fully own the meta title and meta description (so you keep using that plugin’s own editor UI for those). The structured data (JSON-LD) this plugin adds is separate and additive – it will not remove or duplicate anything those plugins generate on their own.

Not if redirects are on (Settings > SEO, on by default). Merging two categories in Merge Terms 301-redirects the old category’s page to the surviving one. For an individual name, open it, fill in “Redirect this name to” with the address of the page you want visitors sent to instead, then move the name to the Trash – the redirect activates as soon as it’s trashed. Neither happens unless you set it up; nothing is redirected automatically just because a name is deleted.

It’s off by default because it can remove a page search engines had already indexed. If your site has many categories or letters with only one or two names each, turning it on (Settings > SEO) can help by keeping those near-empty pages out of results until they have more content – search engines generally rank a site better when it isn’t full of thin pages. If most of your categories are well populated, you likely don’t need it.

The pages follow your theme’s “wide” width by default. If your header uses a different width, set Estasoft Name Catalog > Settings > Maximum content width to match it. If the header or footer itself looks wrong on these pages, untick “Theme header & footer” in the same screen. Note that pages you build yourself with shortcodes take their width from your theme’s normal page layout, not from this plugin.

Install Loco Translate or Poedit and start from languages/wpned.pot. Sorani is locale ckb and Kurmanji is kmr; the files must be named wpned-ckb.mo / wpned-kmr.mo (Loco does this for you). Then set your site language under Settings > General, or use a multilingual plugin such as Polylang, WPML or TranslatePress. First drafts of a few dozen short labels for both dialects are included as wpned-ckb.po and wpned-kmr.po. They are deliberately marked “fuzzy” – a draft by a non-native speaker – so WordPress ignores them until a native speaker reviews each one and clears the flag. Entries marked “LOW…

The link contains only the IDs of the public names on your list, compressed into the address, so there is nothing to look up and nothing stored on the server. Anyone who has the link can see those names, and nothing else about you. Up to your 500 most recent names go into a link.

Settings > Display > A-Z bar alphabet. Choose Kurdish Latin or Sorani. Names already stored as a plain letter followed by a separate accent mark may need re-importing (with “update existing names” ticked) so they sort under the right letter.

Add Male = Boy under Settings > Import. It applies to imports from then on. If both categories already exist, use Estasoft Name Catalog > Tools > Merge Terms to combine them.

Estasoft Name Catalog > Settings > Display > Name list layout > List. It applies to every place names are listed. Switch back to Grid at any time; nothing about your names changes.

Estasoft Name Catalog > Getting Started creates them for you in one click. It only creates pages that don’t exist yet.

Estasoft Name Catalog > Settings > Display > Name cards > Detailed. It shows gender, origin and a short meaning under each name. Detailed cards suit 2-4 columns better than 5-6.

For visitors who are logged in, yes: their list is stored on their account and merged whenever they load a page. Each device remembers what it last synced, so additions and removals both carry over. Visitors who are not logged in keep a browser-only list, and when they later log in, what they saved is added to their account rather than lost.

Somewhat: each row needs one lookup to see whether that name already exists. “Create new” (the default) skips that lookup entirely. Matching is by exact name, and whether “Welat” and “welat” count as the same follows your database’s collation (the WordPress default treats them as the same).

No. After choosing a file, a mapping step lets you match each of your file’s columns to the right field (so a column called “Full Name” can be mapped to “name”, for instance). Your file itself is never changed. Only “name” needs to be mapped before you can continue; anything left unmapped is simply not imported.

Once the import finishes, if anything was skipped, a “Download error log” link appears with the result. It lists the specific row number and reason for every skipped row (a missing name, or “already exists” when Skip existing is chosen, for example) – not just a count.