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 navigation. Attribute: target (same CSS selector as a [wpned_search] on the same page, so letter clicks and search/filter changes drive the exact same results instead of conflicting). [wpned_of_day] - a featured random name, refreshed once per day. [wpned_popular gender="girl" count="5" title="Popular Girl Names"] - a simple popularity list. [wpned_ranked_list gender="boy" count="20" columns="3"] - a "Top 20" style multi-column list with a save/favorite heart on each row. [wpned_favorites columns="3"] - shows the current visitor's saved names (stored in their browser, or synced to their account if logged in), with a "Print this list" and "Share my list" button. Put this on its own page (e.g. "My Namelist") and add that page to Appearance > Menus - no extra plugin setup needed. [wpned_compare slots="3"] - lets a visitor type/pick 2-3 existing names and see them compared side by side (meaning, gender, origin, pronunciation). [wpned_sibling_generator columns="3"] - pick one name, get suggestions that share its origin and/or gender - a "goes well with" tool that needs no extra data entry. [wpned_random label="Show me a random name"] - a button linking to one randomly chosen name, picked fresh each time the page renders, equally likely regardless of gaps in your database's ID numbering. [wpned_roots orderby="name" limit="500" min_count="1"] - the Root Dictionary: every linguistic root that names are built from, grouped alphabetically (or orderby="count" for most-used first), each linking to a page listing every name that shares it. [wpned_swipe] - shows one random name at a time; swipe right (or Save / right arrow) to add it to the visitor's Namelist, swipe left (Skip / left arrow) to move on. Options: gender="boy", origin="kurdish", favorites_url="/my-list/". [wpned_name_combo] - lets a visitor type a first, optional middle, and last name and see the initials, a rough syllable count, the rhythm, and how the names hand off to each other. Worked out entirely in the browser; nothing is stored. Every feature above is also available as an editor block (search the block inserter for the feature's name, such as "Name search" or "A-Z bar") and through the shortcode builder on the Getting Started page. Every name page also has social share buttons built in automatically (X, Facebook, WhatsApp, Pinterest, Telegram, Copy Link - choose which ones appear in Settings) - no shortcode needed.

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 </script> 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 under a randomized filename in a directory with directory-listing and direct-access blocked, and are deleted once the import completes. No content is deleted on uninstall unless you remove it yourself. Imports and exports process in small background batches, so files with hundreds of thousands of rows will not hit a server timeout. An optional FULLTEXT search index (Settings > Advanced) suits large directories (roughly 50,000+ names) by giving search a real MySQL index instead of pattern matching, which can't use one at all. Off by default; reversed automatically if the plugin is ever deleted. wp wpned import <file> (WP-CLI) reuses the same import logic as the browser importer, but processes a whole file in one pass - faster for a one-time bulk load than the browser importer, which is built for smaller day-to-day additions.

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 content isn't lined up with my header/footer. 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 CONFIDENCE" need the closest look. Sentences were left blank rather than guessed. The plugin's on-page messages (search status, sharing, name checker) are translated too, since they come from the same files.

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. The A-Z bar doesn't have Ç, Ş, Î... or my Sorani letters. 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.