cleancoded

I haven’t personally used it, but the weForms contact form plugin (https://ww.wp.xz.cn/plugins/weforms/) has a free tier/option, which includes unlimited form submissions and requires a paid upgrade to connect with third-party APIs like Zapier, AWeber, Google Analytics, MailChimp and a variety of payment gateways. If these are not needed, this might be a good option.

This free plugin includes built-in “entry limitations” functionality that seems to provide the functionality you’re looking for — limiting submissions and displaying a customized notification to users when the form limit has been reached.

Additionally, here’s a step-by-step walkthrough I found for setting this up, originally posted in February of this year (I also checked, the plugin is compatible with the latest version of WordPress with an update just last week):

https://wedevs.com/113912/form-expiration-entry-limitation-wordpress/

Like most things related to WordPress development, there are more than one way to do this successfully. Are you currently using something to manage/create events on your WordPress site? If so, this may influence the form solution (the events solution you’re using may already have a form integration available that would work better than something else).

I have done this before, for a Technology events startup, who needed to limit entries to specific events, and after a certain number of sign ups, inform users that they were being added to a waiting list (or with some events, simply disable further registration).

The solution I chose leveraged gravity forms (a paid plugin) and gravity perks extension that limits entries (a paid extension).

Some more information about this set up is here:

https://gravitywiz.com/documentation/gravity-forms-limit-submissions/

GF does have built-in form submission limiting, and this plugin could be extended exactly how you are looking for (with custom messaging after limits are reached, as well as routing emails to a different list or recipient based on limitation status, or even conditional business rules for submissions based on the limitation status) with some custom PHP and development effort, but I chose the paid plugin because the client was happy to have the issue resolved quickly.

Along these lines, I think just about any form solution could be extended or customized to provide the functionality you’re looking for, and each approach would have advantages/disadvantages relative to your site and business needs, as well as varying levels of time and effort needed.

Here are some typography best practices I usually recommend to clients:

When making decisions as to which fonts and styles to use on a website, it’s important to establish a “visual hierarchy” of content that is both aesthetically pleasing and creates distinction between Headings, Subheadings and Body text. I also recommend using enough white space between blocks of text in an effort to promote an effortless reading (user) experience.

Body text

• The most common font size for Body text is 16px (or, better yet, 1em).
• Avoid center-aligning your text, the uneven edges are jarring. I usually set the left and right margin of the text’s container to auto.
• Justified text works great for newspapers, not websites.
• Choose low-contrast fonts over high ones.
• The optimal line-height of paragraph text is between 1.25–1.5× the font-size.

Headings

• The average font size for Heading text is somewhere around 36px (or, better still, around 2.25em).
• Always prioritize readability and overall user experience. Make sure the headings are not too big or bold or otherwise overpowering.
• That being said, you also need to make sure that your headlines meet readers’ expectations. Considerably larger text with ample spacing between its child paragraph signifies a change in subject matter, whereas smaller headlines much closer to paragraphs imply that the content is related.
• In the event that your headline MUST wrap to the next line, the optimal line-height for headings is less than what it is for Body text.

In general, I’d also be sure to not overdo it and use way too many fonts. I would say 2-3 fonts on any given page, including whatever font you may be using in your logo, is enough. Typically this means one font for headings, one font for body text and MAYBE another for subheadings.

To your question about performance — the more fonts you use, the more resources your site and server have to load. There will absolutely be an impact on performance, so this is another reason to keep font choices very specific and limited. I’ve heard compelling arguments for and against serif/sans-serif/mixing serif fonts, and I think this is mostly a matter of personal preference. I would lean toward overall legibility and user experience — if certain fonts make your text easier to read, I would make decisions accordingly.

The login page is loading for me:

View post on imgur.com

Can you try clearing cache, or accessing from an incognito browser?

You don’t have to change the Function name. You can, as long as it’s the same in both places. Also, it does not matter where you add this function to your theme’s functions.php file. Sometimes you have to add a function before calling the filter, and a priority order, but it should not matter with this function.

On testing, however, I see that I was mistaken on this functionality working for image galleries, it does not.

To update the default image linking behavior for image galleries, please use this function:

add_filter( 'shortcode_atts_gallery',
    function( $out ){
        $out['link'] = 'file'; 
        return $out;
    }
);

Here is an updated video outlining the new Function, and how it works with the default linking behavior for galleries on a new install of WordPress:

• This reply was modified 7 years, 7 months ago by cleancoded.

On line 6, remove this:

t1.meta_value as price,

On line 18, change this:

{$table_prefix}posts.ID ORDER BY if(prior = '' or prior is null,1,0), prior DESC, if(date = '' or date is null,1,0), date ASC, if(price = '' or price is null,1,0), price ASC,

to

{$table_prefix}posts.ID ORDER BY if(prior = '' or prior is null,1,0), prior DESC, if(date = '' or date is null,1,0), date ASC,

I also replied on your pastecode link.

Do you still have the site files and database used to migrate the site to your current host? If so, you probably have what you need to roll back your site on your own. If not, you can reach out to your host to ask if they have a backup of the site at anytime before the automatic updates were made.

In regard to the updates — custom-built WordPress plugins should not update automatically, so it’s probably just an issue of the custom plugin not being compatible with the latest version of WordPress, which may be easier to update than trying to find a backup file from your host. Or maybe not, it depends on what those plugins look like and the functionality they provide.

I only bring that up because you mention you’re currently in the process of having your site rebuilt, and your current developers may be able to review and resolve the plugin incompatibility issues.