I think your custom template name needs to be one word, and that should also be template filename… at least that works for me. Must go in main template folder not child theme.
Note the first item in best of forums?
try disabling all your plugins.
You might try uploading the latest version included with the theme?
It’s unrelated to TagDiv — they don’t own it or make it.
See the docs here for using the optional speed booster plugin; most plugins will NOT work with it unless you expressly add the plugin to the move list. The booster plugin works by moving and optimizing plugins when they load; but if a plugin doesn’t work that way, booster has to be disabled to avoid a conflict.
The docs here describe a method to add the plugin you’re using to its internal list. 🙂
(I don’t work here; just food for thought)
Reading the tips on GTmetrix.com when you analyze your website issues, is super useful. They even make optimized images for you of the worst offenders.
That’s an issue with your site setup, not the instructions. “Are you sure..” is a common error with some WP setups (Google it).
If your setup is not allowing the upload due to permissions or timeout, the best way is via FTP; unzip on your hard drive, then upload the theme folder into the /wp-content/themes/ folder.
Could be a plugin causing issue, or caching, or any number of things. Not issue with theme, thankfully!
Did you follow the normal procedure, per the WordPress codex, for making new page or post templates?
need to have cURL running on server; or install the plugin via FTP from the ‘all files’ download zip, under /plugins/ 🙂
For photos;
you need to upload optimized versions to begin with; obviously a 250kb image that should be 50kb will be problem with speed. Some plugins like ‘smush it’ or similar can help. If your host supports mod_pagespeed, that can also resave large images in faster formats like webp.
For thumbs, try changing default compression level (e.g., ’60’) in your wp-config.php file, then “regenerate thumbnails” to redo all those at smaller sizes.
-
This reply was modified 8 years by
simchris.
Note the drop down menu top of the page:
Documentation > Tutorials
>> https://forum.tagdiv.com/the-child-theme-support-tutorial/
>>> https://forum.tagdiv.com/how-to-make-the-site-faster/
>>> Best of Forums
https://forum.tagdiv.com/best-of-forums/
Did you check your post with GTmetrix.com ?
Did you review my long tutorial on how to optimize your site?
Did you look at the tutorials in the docs section on suggestions for speeding up site?
All good places to start 🙂
Check your meta data to make sure you have proper twitter and open graph tags in place. Test one of your posts with the Twitter developer checker.
Check your php settings in your hosting panel.
Theme has no control over that.
Nov. 29, 2017
==============
WordPress versions 4.9 and earlier are affected by four security issues which could potentially be exploited as part of a multi-vector attack. As part of the core team’s ongoing commitment to security hardening, the following fixes have been implemented in 4.9.1:
Use a properly generated hash for the newbloguser key instead of a determinate substring.
Add escaping to the language attributes used on html elements.
Ensure the attributes of enclosures are correctly escaped in RSS and Atom feeds.
Remove the ability to upload JavaScript files for users who do not have the unfiltered_html capability.
Yes. I posted a tutorial thread in the docs > diy / tutorials > best of forums.
There are others on here as well. Mine is a little hard to read in places due to the formatting getting minified with last update to this forum, but it’s a good starting point amongst others.
You can also learn a lot by testing one of your posts with GTmetrix.com and read the instructions there 🙂
Check your open graph tags setup properly.
If we both stop posting, they will look into it, but likely if my answer is correct one, then may say same thing — normal debug is to look for errors in your log, turn off other plugins, disable any caching or optimization tools, etc. to determine what is causing issue. Especially since theme has no RSS template, as there is no css for that. It’s all done by WordPress — so if plugin breaks that, theme can’t do much about it. But they may be willing to take a look once you identify what steps you’ve done already to debug the issue with your setup. 🙂
Theme doesn’t encode the RSS feed — WordPress does that. So if your RSS feeds work normally with that plugin disabled, but then are mis-encoded when plugin enabled — it’s an issue with plugin.
I don’t work here – but the RSS feed template is not part of theme and just publishes the content from the post box. If you’re using a page builder for a post, that might mess up the characters. Same with certain shortcodes that don’t ‘travel well’ as they are CSS, and there is no CSS in RSS.
Dunno. Sorry.
Simply look at your post meta. If the og tags are there, then they are there. If not then yoast not setup properly.
So, the normal rss feed with theme is also incorrectly encoded, when plugin disabled?
Talk to the person who makes the plugin on how to change the encoding they are introducing. Theme doesn’t control that. Encoding of RSS feed is managed by WordPress, and format of custom RSS made by the plugin is done by them.
Install only the ‘theme’ folder and not the ‘all files’ zip.
Ah, sorry; I guess you meant ‘pages’ not ‘posts’ …
normally in WP ‘pages’ are standalone docs which are meant to be single entities like “about our company” or “contact us” and so would not have tags or categories. “Posts” are designed to have relational data such as “cakes” “pies” or “scones” for an article about recipes.