also useful to see this:
Stay aware, stay on top of this stuff, and stay safe!
A ‘must read’ —
https://forum.tagdiv.com/topic/tutorial-good-basic-security-practices/
Groovy!
Still waiting for my unicorn with a crown badge 😉
(kidding)
Thanks for the continued development and support of the theme.
Newsmag is still my fave of the three themes.
Main tricks
1) limit queries ‘per page’ – use maximum of 3 “module elements” per post/page
2) don’t use mega menu with posts
3) use PHP 5.6 and up with opcache ‘on’
4) optimize WP with things like explicit URLs in wp-config.php file
5) to mitigate hacker/bot overloads
— > disable XMLRPC
— > install ‘limit login attempts’ plugin
This helps a *lot* (!).
Also, generally comments don’t work on ‘private’ posts … so obviously if we can’t see your post, the URL to your home page is no help here. 😉
Make sure
a) comments are ‘on’ in the WP admin panel settings under ‘discussion’
b) make sure comments option is ‘on’ in the theme panel under ‘post settings’
c) make sure the comments option is checked [x] yes in the section bottom of your post
Should work for all new posts you do moving forward. For older posts you ‘might’ have to go back and switch on the option by doing group edit from the posts edit screen; depending on how you’ve been handling comments in past.
If using an external comment plugin, that may be completely different problem.
Not sure that helped; but most common issues 🙂
( I don’t work here … )
See the theme docs on how to install the theme. Good place to start:
https://forum.tagdiv.com/newsmag-documentation/
With Advanced Custom Fields (ACF) you would use [shortcode] in the post box.
Normally with WP post meta custom fields, you would put those in your theme template.
FYI:
https://codex.wordpress.org/Custom_Fields
https://codex.wordpress.org/Post_Meta_Data_Section
Or you’d need to use a plugin or function to enable WP post meta to be used with [shortcode] vs php function calls, as in template loop.
For those who got lost from above:
a) how to scan your site with free Securi site scan — may not catch everything, but good place to start:
https://sitecheck.sucuri.net/
b) WordPress offical docs (codex)
— on “security hardening WordPress”
https://codex.wordpress.org/Hardening_WordPress
–> includes suggestions for changes to .htaccess
–> stop php execution in uploads folder
–> disable XMLRPC
–> edits to wp-config.php
: secure the file
: disable core file editing from WP panel
c) Official WordPress security updates log
https://wordpress.org/news/category/security/
d) WPscan WordPress vulnerability log
https://wpvulndb.com/
e} Security Plugins
While there are many to choose from, an essential one we use here:
* Limit Login Attempts
https://wordpress.org/plugins/wp-limit-login-attempts/
You should be checking these — hacker sure are !!
Yes, the version was 6.71. Fixed April 2016.
See my tutorial on security practices.
Tagdiv likely needs to put sticky notice top of forum.
Its the same with wordpress prior to 4.7, also insecure and hackable regardless of theme.
No malware in theme.
It’s a known bug in one of the demos, where I think it’s a background image you need to delete from the setup in theme panel – but not sure where.
Sorry, don’t work here, but you’re not first with the issue — basically a background image is in there for the demo, but doesn’t work on your actual site (not YOUR fault).
You can keep using Visual Composer – it’s not gone.
For ‘suggestions’ for TD Composer, you might want to send email to team.
Make sure *not* to also activate TD Composer at same time.
Yes ! Likely good idea to popup a banner notice, in admin specifying that TDC and VC should not both be active!
Do you mean it won’t install, or do you mean site stops working when you replace old version (delete), then upload new version to plugins folder?
Compare your menu code to the demo code for theme, to see what might be different due to plugin or other setting ?
Note all modern ‘responsive’ themes may have what look like duplicate links, but are not. Meaning, you may have a ‘switch menu,’ with a larger desktop menu, that switches to alternate menu for phones. Obviously both versions need to be in the code to switch, such as on a phone going from portrait to landscape and this is very common.
Some sites do a more technical ajax menu loading trick, or custom mobile template, but most ‘responsive’ themes may have two menu versions to switch. Nothing wrong with that as the ‘visibility’ is set to only appear on specific devices.
Yeah, old bug in wordpress.
On several of our sites we use Yoast SEO, so we add their ‘glue for AMP’ which solves couple of things. Also, one can simply edit the AMP template, or add functions to it (like, in our case we add a function shortcode for ‘related posts’ at bottom of the AMP endpoint). Not too tough to work with, but obviously many choices. 🙂
Dunno. Try it. 😉
I tend to use the ‘best solution’ for our systems so we don’t have wonky breakdowns during funky free plugin updates. The Automattic version is running on the VIP sites like Time Magazine, etc., so they have incentive to update it for their cash cows. 🙂 SO, in our case the Automattic version is best choice for us.
Facebook only reads the meta data you insert into the header of the posts; theme has no control over anything related to that. Basically, if you view source and your OG data is there, then it’s an issue on FB’s side — either your site, or their system is ‘timing out.’ You can try the FB debugger, but not much more you can do except ‘refresh capture’ from the post, or clear the FB cache via the FB console.