Tim Nash

You can’t is the simple answer, if your content is public it can be copied, you can try and implement various form of copy protection but anything implement can be worked around.

Preventing people right clicking, is pointless as you can just keyboard or the menu, it just means you are making life awkward for yourself.

I’m afraid it’s one of those things that just happens, you can look at attempting to have sites taken down through legal channels or you could prevent the sites getting access through putting it out of the public domain, behind some sort of login.

Ultimately that’s the only way to prevent such actions.

require_once( get_stylesheet_directory() . '/admin/main/options/02.homepage.php' );
will load the specific file or if you prefer

$options_path = get_stylesheet_directory() . '/admin/main/options/';

Will set the variable with the path to the options folder.

ok you have 2 issues here:

1) Licensing
2) Doing

I am assuming you are running a self hosted blog where you have access to the files and can make edits? i.e you are not running example.wordpress.com

1) Themes should be Licensed under GPL which means you can do what ever you like to the theme as long as you obey a few restrictions in terms of redistributing and authorship. This means you are free to remove the “blog credits” in the footer, though it is good practice to still keep the credits and explain the original ownership within the code for example in the styles.css along with your details.

Some themes might license in a different way, they shouldn’t and if they do well that’s naughty but in such cases, it’s up to you if you feel you can remove the credit. Some ask that if you remove credit links you give them a few bucks again you can just remove the credit links in the footer regardless, as long as you do accredit them somewhere.

2) The actual removal, is a case of opening footer.php finding the html with the credit and deleting or replacing as you see fit.

Now for the moral bit, people work hard on developing themes so think long and hard before removing credit links to other peoples works. If the link is back to the author of the theme (and not another random company) then it’s a way of saying thank you to them.

Up to you if you want to remove it, change it or do something else, but remember the work someone put into it.

When you go into the post in the admin area to the edit screen, on the right hand side you should see the category list? Do you see newsletter option ticked?

If not tick the box and hit update and it should appear.

Rather then doing it in the theme customiser, if you go to Settings -> Reading and set the static page there, does it work?

As it’s a Yoast Premium question, you are best of using their support methods, I believe they have a dedicated support email.

However the do_action

is a trigger, so other plugins including Yoasts plugins can hook in and do actions at that point in code, in this case template redirect.

So any plugin, theme or indeed WordPress core can call that function and add their own redirects at that point. When you commented this out, you stopped everything from using this ability.

Tracking down all the actions associated with a specific do_action can be a little awkward

If you are happy getting your hands dirty you can look directly at the $wp_filter – http://wordpress.stackexchange.com/questions/17394/how-to-know-what-functions-are-hooked-to-an-action-filter

Otherwise you can use the debug Bar addon https://wordpress.org/plugins/debug-bar-actions-and-filters-addon/

However that might not work with redirect as you need to be on the page template as its being called.

One final thing do not remove that line it’s really important 😉

When you removed the ad code, you didn’t quite remove all of it, so part of the script is running causing your issue which is why you also have stray characters showing on the screen. You will need to go back into your header.php file and make sure you have removed all the code, and closed any <script> tags with </script>

So looking at your site with – http://gtmetrix.com/reports/aysomusic.org/vsvRqmVL

The issue is the sheer number of get requests you are making on each page load, if possible you want to look at combining some of those css files and js files. You could also look at something called Lazy Loading, to defer loading unessential content till after the primary content is loaded.

Finally enabling things like gzip and minifying content will help as well.

Caching will not actually make the number of requests lower but caching plugins often have magnification tools for minifying and combining. If you have server access consider installing mod_pagespeed.