Scott DeLuzio

What is your site? Does the message say anything else, like what file it is looking for but doesn’t exist?

You could disable the visual editor for the users who need to update that page. The CSS would still be editable, but the formatting wouldn’t accidentally get updated by the visual editor.
Just update the option on the user’s profile – see screenshot

Thanks for the response. Like I said, I wasn’t entirely sure how to best implement an idea like this, or even if it was a good idea to do. After reading your response, I’m inclined to think that perhaps it isn’t as good of an idea as I originally thought.
Maybe a better (or at least more secure) feature would be to encrypt the brute force passwords in the database. Anyone who suspects another account has been compromised (their email, social media, etc.) could check their password through a form in the admin to see if it matched any of the passwords used in the brute force attacks. This would help confirm that the other account’s password needs to be changed in addition to the WP password.
Nothing would be saved in plain text, and would only indicate a yes/no response if an entered password matched any of the passwords used in a brute force attack.
Again, I haven’t thought through all the details – just offering a suggestion. Thanks again for your response.

This is only an option in Version 2. You probably are using version 3?
If you are using version 3, go to settings (Settings > SyntaxHighlighter) switch to version 2, and check the Wrap long lines box in the Miscellaneous section.

Wonderful! Thanks so much for your response.

I think all it would take is removing the http: from line 402 of /wp-portfolio/lib/thumbnailer.inc.php

Line 402:
$imagefile = sprintf('https://images.shrinktheweb.com/xino.php?stwembed=1&%s&stwurl=%s', http_build_query($args), $url);

Change to
$imagefile = sprintf('//images.shrinktheweb.com/xino.php?stwembed=1&%s&stwurl=%s', http_build_query($args), $url);

Easy Digital Downloads can be used for events/classes like this.
I have used it on several sites and it would meet all your criteria:

• Easy to add new “classes” – just like adding a blog post with a little extra information (cost, etc.)
• Out of the box uses PayPal for payments, but other extensions are available to accept payments through other processors as well
• Since it is designed for digital downloads, there is no shipping information collected, which streamlines the checkout process
• Made for downloads, but can be easily modified to be used for services like a class.

You should be OK with 644 or 600 permission on wp-config.php.

See the documentation here: https://codex.www.ads-software.com/Changing_File_Permissions

The exception to that, since you mentioned you are on shared hosting, is if you are on shared hosting with suexec, in which case:

wp-config.php should be 440 or 400 to prevent other users on the server from reading it.

https://codex.www.ads-software.com/Changing_File_Permissions#Shared_Hosting_with_suexec

Additionally, if you are worried about someone accessing your wp-config.php you might want to check out how to secure wp-config.php here: https://codex.www.ads-software.com/Hardening_WordPress#Securing_wp-config.php

There are other security considerations you might want to loo into as well on that page: https://codex.www.ads-software.com/Hardening_WordPress

Hope this helps.

Hi Sally,
Try adding the following CSS to your theme’s style.css, or if your theme allows for custom CSS add it there:

.dd_button_v a[data-pin-log="button_pinit"][data-pin-config="above"] {
    margin-top: 30px !important;
}

Yea that is something I would eventually like to include with the plugin also. Seems like it shouldn’t be too difficult, but I also don’t want to make the page a mile long if someone has a bunch of shortcodes with tons of arguments. Maybe a tooltip/hover type setup that populates with each shortcode’s arguments would work?

Great suggestions. I originally set this plugin up because I had a site that used a bunch of shortcodes for various purposes and I could never remember what they all were. I found myself searching all of the plugin’s FAQ pages or support threads to remind myself what each plugin’s shortcodes were.
This just made my search a little easier. Ideally I would also like to include some information about variables that each plugin can use (i.e. [shortcode url=””]).
I also haven’t had a ton of time to devote to this, so if you happen to come up with any improvements please send them over and I’ll update the plugin with proper credit.
Thanks!

The plugin was only designed to handle one field for right now. I started working on another version that will handle more fields, and will post an update when it’s ready.
I’m glad you are enjoying the plugin!

The plugin uses the ad code that you insert in the plugin settings (WP Admin > Settings > Adsense In-Post).
Once you paste your ad code in one of the blocks, use the appropriate shortcode ([AdSense-A], [AdSense-B], or [AdSense-C]) to insert the ad code inside a page or post.
If you want to use the shortcode in the sidebar, your theme may not allow shortcodes in a text widget. If that is the case, create a child theme, and add add_filter('widget_text', 'do_shortcode'); to your child theme’s functions.php file.

For anyone else trying to figure this out, I found a quick fix:

1. First create a child theme if you aren’t already using one.
2. Copy front-page.php from /wp-content/themes/Tidy to /wp-content/themes/Tidy-child
3. Somewhere around line 98 in front-page.php (in your child theme), is a line that starts with $tidy_blogargs = array( 'posts_per_page'
4. Just before that line insert a new line with the following code $paged = (get_query_var('paged')) ? get_query_var('paged') : 1;
5. Inside the original $tidy_blogargs array, insert this line 'paged' => $paged, immediately before the 'tax_query' line.

This will get your /page/2, /page/3, etc. URLs working if you manually type them into your browser, but you still won’t have the navigation links at the bottom of your page.

To get those navigation links, find the line with </section><!-- #blog-area --> and insert the following code directly before it: <?php tidy_paging_nav(); ?>

Hope this helps.

There was a bug in the plugin that was preventing the required field option to be switched to “No”. I just pushed out an update, which should address this issue.
You may need to go in to the Conditional Field settings page and save the options with the required field option set to No before the plugin will work correctly.