List of modified files for version 6.6.1

Hello

I can’t find the usual List of Modified files for the update 6.6.1 that just went live…
Any idea ?

Thanks

It would be nice if there were patch notes on each release.

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.

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.

Over looked the update_log.txt, the web sarcasm was not appreciated. Thank you though.

I don’t download the them file… I update it directly on WP…

And as you can see… it doesnt show the modified files… I have to know which files have been changed..

• This reply was modified 10 years by byothe.

No, they arent specific enough. The document only list files changed between 6.5 and 6.6.1, not between 6.6 and 6.1.

Anyways, I guess its just the social plugin but the the documentation should be more specific.

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. ))

As I said, its not specific enough.

The documentation has two parts, the update log and the changed files. If there are no files changed in the theme, that information should be visible; not everyone has ages of experience updating this theme so this kind of help file is more handy for them than your sarcasm or the “look for stuff” answer.

If some says “I can’t find the usual List of Modified files for the update 6.6.1 that just went live…” it’s because he already looked for the file and wasnt sure about the changes.

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.

@Chris S
You are just so arrogant…

Why yes, yes I am. You’re most welcome 🙂

At least now you know where to look.

And the same goes for 6.6.2. There is no updated files document. So in Chris logic, the new update doesnt update any file. :v

@Arved007
grow up sometime this century, why don’t you?

• This reply was modified 10 years by simchris.

Ah, come on , Chris it was just my “bent sense of humour, bordering on sarcasm”.

As I said in my first post, the updates file should be specific enough: if no changes are made to core files, that info must be there listed. If some files were changed, the list of them must be included.

Not anyone knows when something was forgotten and when there arent any changes. The update info should be specific enough for anyone that buys the theme.

And when someone asks for help, they need help in a good way, Chris, like most of your posts in this forum. Not sarcams that very often is missundertood with mockery. 🙂