Right…. there were no modified files. Self evident from the changelog.

if the changelog says nothing was updated in theme, no reason to list the changed files as there were none.

I suppose they could put note at top “No changed files” ….

I’m sure TagDiv will provide a canned answer for THAT suggestion 😉

Also to be fair, my semi-sarcasm was directed at the trolling comment “It would be nice if there were patch notes on each release.” which would have been more useful as “where can I find the changelog?” …

But point taken. I guess I should not bother to post answers to stuff like this, really.

Still, hopefully somebody reading this will now know where to find the changelogs.

Admin, would be useful to make note in the documentation on theme updates, on “where to find the changelog” — like here … https://forum.tagdiv.com/how-to-update-the-theme-2/

This phrase “Always check our update notes” is not specific enough for most folks here, apparently.

And thus why the enacted a registration system, and proof of registration to get support.

Really sad that pir8s don’t believe anything has any value in this world.

There are no file changes between 6.6 and 6.6.1 — if you read it, the only change was the plugin:

[ Version 6.6.1 ]
– new social counter version. Facebook requiers now an API key, read more here: https://forum.tagdiv.com/tagdiv-social-counter-tutorial/

@byothe

the only way to get the changelog is to download the files from Themeforest, and unzip on your PC. There used to be a changelog “page” on the TagDiv site once upon a time, but I think they removed it. They sometimes also post that on the theme page on Themeforest, but not sure they still do that, and there is delay. Getting the “actual” files is always the best way.

In other words, if you are interested in which files changes, such as for customizations, you don’t do mods to pages in the theme panel, but offsite via editor. You should never edit theme or core files in WP via the admin panel, only outside of WP.

(( I don’t work here, just pointing out that those who need help on stuff like this can often help themselves if they bother to look. Sorry if nobody appreciates my bent sense of humour, bordering on sarcasm. But, come on people, go LOOK for stuff – it’s not that hard. ))

and, oh my gosh … it’s still there!
I guess the file names “update_log.txt” and “changed_files_6.5_6.6.1.html” are not specific enough?

===
NEWSPAPER THEME

Thanks for your support and feel free to contact us any time 🙂
https://forum.tagdiv.com/

~ Radu, Marius, Emil, Alina, Lucian, Nicu G., Alin and Nicu S. ~

[ Version 6.6.1 ]
– new social counter version. Facebook requiers now an API key, read more here: https://forum.tagdiv.com/tagdiv-social-counter-tutorial/

[ Version 6.6 ]
– new: Custom code panel. We realized that all the custom css, html and javascript should be in one panel. We also added a custom HTML code section. All the input areas from this panel have autocomplete (ctrl+space) and error checking.
– new: whatsapp share for article on mobile devices
– new: added http channel test status in the system status panel. You can now check if the theme is able to get the tweet count, like count etc from your host.
– new: filter posts by ID in blocks. You can add/exclude specific posts on all the blocks now.
– new: the theme now has it’s own logging system. We can now debug hosting issues easier.
– new: a new self diagnosting and self configurating module that allows our theme to pull data from other sites more reliably.
– fix: smart list 7 and 8 – sometimes the content was doubled
– fix: g+ new icon
– improvement: video playlist is now more reliable and all the code is loaded only when needed via autoload. The youtube videos information is now collected using just one API call instead of multiple API calls for each videos.
– improvement: speedbooster 4.2 now supports woocommerce better and moves the style.css to the bottom
– improvement: the theme panel works better now when adblock is used
– improvement: all the ajax functionality of the theme is now loaded only when needed
– improvement: better security checks on all the ajax requests
– improvement: html is allowed now in the copyright section of the footer
– improvement: social counter button is clickable on the entire area
– improvement: almost all the javascript code now passes jshint. We still have about 15-20% of the code to refactor to the new standards but with time we will get there.
– improvement: the theme’s data source class can now be overwritten from the child theme
– improvement: all the widgets from the theme are now optimized to work better. The widget_builder class is now deprecated and all the functionality was moved to td_block_widget
– improvement: the video playlist now downloads the videos metadata on render, not on save post. This allows us to use the playlist on the on click demos.
– improvement: the following modules of the theme are loaded on demand now: td_log, td_remote_http, td_remote_video, td_data_source, td_video_support, td_more_article_box, td_page_views, td_review, td_ajax. This means that the theme loads them only when needed. We mesured a 10% faster load time after this tweak.
– fix: theme animations where incompatible with some plugins and the visual composer gallery. The animations still worked but all of them looked a bit strange.
– fix: bug with the demo loader – the dinamic css for a specific demo was still loaded even after the demo was uninstall
– fix: header style 8 top submenu z-index fix
– fix: image aligment issue when using custom article paddings
– fix: the documentation url for demos was wrong in wp-admin
– fix: we updated the ads links to point to the right documentation
– fix: Social counter now shows the followers instead of +1 on google plus. Please update your social counter to see the improvement.
– fix: styling issues with the latest version of BuddyPress
– fix: on rare ocassions with some plugins the theme was emitting warnings in the server logs like: “Catchable fatal error: Object of class stdClass could not be converted to string”
– fix: error that was showing up in logs when the theme panel was saved

==

• This reply was modified 10 years by simchris.

These are usually included in the download of the files from Themeforest; at least the ones I’ve been downloading the past 2 years. Might have changed. I have not yet download the latest files.

Well.. it makes the site compatible with the AMP protocol. If you read-up on what that is, it’s self explanatory.

It creates a super optimized version of page for mobile which loads at pagepermalink/amp/

I was curious of anybody had tried it yet with TagDiv themes, or just *any* WP website at all?

forgot to include link to plugin in repo:
https://wordpress.org/plugins/amp/

I guess the main thing it does is strip out javascript ?

Not a lot of info out there yet — like in our case running mod_pagespeed would it be necessary?

Likely plugin not compatible.
Best to disable it, then you should be able to login.

If you cannot login to your admin panel,
you will need to go via FTP, or your host panel,
and change the /wp-content/plugins directory to something
like x-plugins temporarily.

This is how you reset all plugins to off. You should then at least be able to login.

Then you can remove the bad plugin from that folder.

Then rename it back to ‘plugins’

6 month support was set by Envato/ThemeForest not the theme devs.
Also, they are closed weekends, as noted top right of forum.

For support, you need to be specific, and include link to a post/page showing example of problem and/or screenshot — this helps the support team, as well as some of us who use the theme daily (in my case over 2 years with TagDiv themes).

Note theme support doesn’t include basic WordPress self-education. Optimizing your site, server, images, caching, time to live (TTL), etc., are all functions of any WP install. Themes are “skins” on top of that. And, the more complex a theme/page you setup the more resources it takes. A page with 20 images and 20 dbase queries uses 40x the resources of a page with one image, and no “related posts” and other stuff.

There is a decade worth of help online on how to optimize the speed of your site for WordPress you may find useful doing Google searches, also.

TagDiv support does a great job providing support; however, they also get a little behind when there are too many queries like “how do I upload a photo” that can be found from the normal WordPress docs.

TagDiv are awesome because they DO try to help people with the newbie stuff that most other support folks won’t bother with and just point you at the RTFM docs at WordPress.org (the “codex”).

If you can be very specific about your issue and what you did to try to mitigate it, they are very happy to help — which is truly remarkable these days.

Wasn’t putting you down, just some feedback to your feedback. 🙂

Omar,
you might try using the built-in grids for the theme first since those do work, and then try customizing from there.

I think we chose to use opcache/APC + mod_pagespeed here …

but Varnish has been around quite awhile — lots of folks use it with NGINX server setups, especially. We’re Apache-centric here (at my company) so we’re kind of using the stuff built into Apache, CentOS, Plesk, where possible.

Waiting on HTTP/2 support to get one dot newer with Apache, as this replaces SPDY and some other stuff and is the cat’s total meow! 🙂

Note theme doesn’t handle email, but I believe there were some changes in WordPress recently in how they connect/send email at server level.

On our particular server (we have our own box, so pretty easy to figure out what is and what is not happening on the WP side) — we could only get email via WP to work CORRECTLY using the “WP-Mail-SMTP” plugin.

link
https://wordpress.org/plugins/wp-mail-smtp/

• This reply was modified 10 years by simchris.

I think that is in the big config file inside the includes/booster folder or whatever it’s called now.

TagDiv will have specific answer tomorrow; but that might give you a head’s up on finding it in meantime. 🙂

Also, many devtools likes Dreamweaver and many programming text editors allow you to search an entire folder to locate a block of text — great tip for locating stuff inside folders inside folders in themes.

a) perhaps post in Newspaper forum for faster reply
b) you often have to regenerate thumbnails when changing themes — NP6 is an all new theme from NP4

Theme docs somewhat useful too:
https://forum.tagdiv.com/newsmag-how-to-update-the-theme/

I don’t work here; just another user like yourself….
I’ve just been through the learning curve about five times, which is why I’m so dizzy! 🙂

• This reply was modified 10 years by simchris.

It’s a built in feature of WordPress …
use the ‘show visibility’ tab top right of WP post screen, to show all the option panels on the post page; one of which is “authors” — which allows you to select an author to attribute a post to. This presumes you actually setup authors (users) for your publication.

The WordPress codex on WordPress.org is a great read in learning to use WP.
see:
https://codex.wordpress.org/Writing_Posts

this shows all the default options for posts, like “post author” 🙂

• This reply was modified 10 years by simchris.

Might be issues with YOAST – major bugs since v3 launched last week — two more fixes today!

3.
you need to select the author on the post page.

and the hits keep coming, in case anybody still following this thread:
— as expected they added t he opt-out of the onpage check — which we also complained about!

==== changelog Dec. 1

3.0.6
Release Date: December 1st, 2015

Bugfixes:
Fixes the recalculate tool that was broken with the Localized Flesch Reading ease change…
3.0.5
Release Date: December 1st, 2015

Enhancements:

Made it possible to opt out from the OnPage.org indexability check.
Contains a few small performance enhancements in the Content Analysis.
Only includes Flesch Reading ease test when site language is set to English, since it doesn’t really add value in other languages yet.
Bugfixes:

Fixes a lot of issues with dismissible notices. Thanks Craig Pearson for writing the patch!
Fixes several issues with keyword recognition for keywords which contain punctuation.
Fixes an issue where keywords containing diacritics were not recognized in alt tags.

• This reply was modified 10 years by simchris.

Also note you can see bug reports for YOAST SEO here:
https://github.com/Yoast/wordpress-seo/issues

note a LOT of people are going back to the 2x version for the time being until possibly a 3.05 or 3.06 bugfix catches up to all use cases — by switching a lot of their core to JS, they ran afoul of how a lot of browsers, WP admin, and other plugins mess with all things javascript/Ajax.

If you are having major issues, it’s “suggested” by a lot of folks to roll back to prior version of YOAST until the dust settles and/or wait for WP 4.4 to come out in a few days (?) where compatibility issues between the two are more in sync.

• This reply was modified 10 years by simchris.

You can often update the default settings from your hosting panel (e.g., cpanel, plesk, etc) under the php settings for your hosting account.

@Magistar

Hi
those remove the WordPress version, the manifest link, the RSD link (Yoast can also disable two of those, but why do it with plgin if you can do it yourself)

the two feed items remove secondary feed RSS like ATOM, and also the comments RSS.

Chris

Best first steps:
Change your theme being used to default WP theme (eg twenty-fifteen)

a) remove/delete all themes except for the 3 default themes with WordPress
b) remove/delete all plugins you’re not using (e.g., old ones from old themes, anything new you’ve installed recently not included with the theme)
c) change *all* your passwords for WordPress, and your hosting account ASAP.
d) reinstall ALL your plugins (delete old ones entirely, replace with new ones via FTP), and download new copy of the theme from ThemeForest — delete old Newsmag folder, upload NEW copy — don’t over-write ANY old folders during this process

dd) install full clean copy of WordPress — do this by FTP; delete the wp-includes and wp-admin folders, upoload new ones from fresh download of WP from WordPress.org; over write the files in root (be sure to backup your wp-config.php and .htaccess files)

ddd) double check your htaccess file for any weirdness such as redirects to other websites

e) rescan your site with SECURI scanner.

If your content has been infected at the post level, you may need to manually edit each post to remove “injected” content.

Once your site is “fixed” — consider reading up on numerous security posts online to do stuff like
a) delete admin account as super user
b) install tools like “limit login attempts”
c) consider disabling comments and pingbacks entirely unless you have need for them; consider using plugin like Disqus instead
d) read up on any plugin on wordpress.org before install; don’t install oddball plugins “free on the web someplace”
e) make regular backups of theme settings, wp settings export, php dbase clone and save, etc., full ftp download of all assets to local drive

Hopefully that all may give you some guidance and perhaps starting point on some things you can do yourself before finding somebody to hire.

Generally Google likes the date if you have an actual “news site” or blog vs advertising or corporate site. Be aware they keep track of the date they first capture the content from your sitemap regardless so you can’t trick them into saying something is 10 years old when it’s 10 days old. Ideally the date is also used to identify ‘updates’ to content to ensure Google fully re-spiders a page for better SEO and relevance.

If you’re not running a news portal or blog, you obviously don’t need the “date” on a page, but posts are usually intended for time-specific content — if you comment on the holidays, it’s useful to know what year the holiday is you’re writing about for context. If commenting in a “post” about your new iPhone, useful to know what year that is, also.

There is no harm in having a date. For example even on “pages” it’s useful to have a copyright date in the META depending on your use case.

Just some thoughts on a pre-Thanksgiving morning here in Calif.

:-0

Check your site here for issues that might be fixable:
https://gtmetrix.com/reports/histaminentzug.de/HyYnYkEV