It also works perfectly with WooCommerce and popular builders like Elementor, Beaver Builder, and Divi.

Thanks!

I have a CPT ‘Elections’, with one template and one listing that applies to all elections posts. (I am using JetEngine and Elementor).

Elections posts include Governments (e.g. United States), Offices (e.g. House of Representatives), Districts, Primaries, and General Elections. Some of these overlap (e.g. House of Representatives District 10 is a General Election page).

As a newbie to web development, I’m struggling to figure out how to build this out logically so that I can easily improve the user experience.

I have set up taxonomies to organize posts by: election type (primary, general election, NOT an election (e.g. a government or office with districts)), government level (governments, offices, districts), and years (2023, 2024, etc. (which affect if the post display results or upcoming election information).

Unfortunately there is so much conditional logic combined with a so-so (yet improving) naming structure, that changing anything in the listings, is difficult to think through, implement, and test.

I just set up a staging/dev environment. (Thank goodness). I plan to get a whiteboard to visualize the database and site structure. But I’m still in this strange place where I have little experience and limited resources to have an experienced dev manage the structure.

I have tried building out separate post types (e.g. Governments) and I may return to that, however, the last time I did this I bit off more than I could chew and ultimately returned to the current structure.

Any thoughts/suggestions for improving the site’s structure (or perhaps finding local development resources for a bit of ongoing advice) would be greatly appreciated.

Thank you!

I want the admin domain to host everything for administrating task such as login and content editing and let the other domain to be used for public users.

However, during the content creating in the admin domain, such as inserting images, WordPress stores the data inside the database as an absolute path, which includes the admin domain instead of the public domain.

Is there any way to make the content management utilize the public domain while still maintaining the use admin domain to access admin pages?

Thank you.

I want to build a client portal. Each user has their own private space to log where they can see everything about their account.
I need to update their information from time to time – in bulk mode – (which campaign are they assigned to, an url to that day’s invoice, etc) without deleting past information. Want them to have an archive of the information I upload. Since

Basically, I have 3000 clients and each one has different informations (url to pdfs, campaign dates, campaign details, etc) that I need to upload montlhy or every two weeks. But I need to upload on a bulk mode, through an import or something..

All I see is imports based on user groups, nothing individually.

Hope I explained myself correctly

It’s very accessible for non-techies meaning you can have a decent looking site for a low learning curve but must save techies so much time too.

*most importantly* – Elementor does not leave so much dag behind when you stop using it – like others certainly do. There is also a free version, so you are not enslaved to a paid subscription to make your site just work, after you have started designing with it, then choose to use something else.

It integrates well with other WP building tools too. e.g. you can use shortcodes to inject an elementor-designed element into a page or post, even if built with other tools like Gutenberg or Brizy for instance.

Templates – Really powerful (a Pro feature) is the ability to build themes and styles for specific content types and when certain ‘conditions’ are met. i.e. anything in this category or this post type, display in this template or that template. This is great for Content Management, Listings and Directories sites – those using Custom Post Types. Or sites with multiple authors – if this author, show this template if that author that template.

It’s clearly a loved plugin by the developers, well thought-through with constant updates and now it’s also very well-bedded into being a mature and stable plugin. The growth in its usage speaks for itself. The massive user base also means there is someone in the community who knows how to fix any typical problems you may encounter.

Great little idea which has clearly solved a very common problem!