[jennmattern]

“Renewing the support license is not related to viewing the changlog, you can always view that and get updates regardless of what TF does next…”

That’s my point. I shouldn’t have to renew a support license through TF just to access the forums here (which you noted I would need to do) to ask for proper changelog information every time there’s an update. I didn’t come here to ask for support w/ the theme — just the info that should be in the changelog, which I already have access to, in the first place.

[jennmattern]

Thank you.

And I have no intention of renewing a support license w/ TF just to get proper changelog details. I’m already in the process of redesigning the sites on other themes, moving away from all ThemeForest products (I have no tolerance for any company changing policies after one-off purchases have been made — and yes, I know that wasn’t Swift’s decision).

[jennmattern]

Thanks a lot!

[jennmattern]

Do you have the changelog for this version? That download looks like it’s the WP files, but not the full typical TF download that has the changelog info. I just need to know which specific files were changed from 1.66 to 1.67.

Thanks again.

[jennmattern]

Thank you very much!

[jennmattern]

Nevermind. I think I found all the references. To make life easier, I’m just copying the entire /includes/page-builder/ folder from the newest version. If you’re aware of any other prettyphoto files outside of that directory, please let me know if you get the chance.

[jennmattern]

Hi again guys. I’m trying to get this site updated, but the changelog isn’t listing specific files that were altered. I’m not worried about RevSlider because I don’t use it (haven’t uploaded it anyway), but I’m concerned about the PrettyPhoto security vulnerability mentioned in the screenshot Ed posted a link to. Any idea what files were changed for that?

As for you guys thinking about setting up shop outside of Envato, that’s great news. I’ll keep an eye on updates here because I’d hate to lose your future themes in my plans to ditch Envato.

[jennmattern]

Thanks Ed. I must have downloaded the WP-only fileset from TF. I’ll check out the other one later today.

The version that’s out of date is the changelog that appears publicly on the TF page for Pinpoint. It’s about 2/3 of the way down this page if you decide to update that too:

http://themeforest.net/item/pinpoint-responsive-multipurpose-wp-theme/3760530

Thanks again!

[jennmattern]

Thanks Kyle. 🙂

[jennmattern]

Are you guys planning to release changelogs with each update at least? That’s the main thing I use the forum for — trying to get a list of changed files because I run manual updates due to complicated site setups. It looks like there’s an updated changelog for Flexform on TF, but the one for Pinpoint looks outdated. It hasn’t been updated since Jan. 2014 for version 1.6 while they have 1.6.5 available for download now.

That’s what I came here for today, and this is the first I’ve heard about the changes. Unfortunately I’ll probably start moving away from all ThemeForest themes (truly love you guys, but on principal I won’t continue supporting companies that change things for customers long after a purchase was made, which is what they’re doing by dragging devs into the new policy when they had other, better, support structures already in place).

Knowing whether or not changelogs will be kept up-to-date will at least let me know how quickly I have to prioritize the moves and redesigns. Any info you have about that would be appreciated. And it would be awesome if you guys could update Pinpoint’s public changelog on Themeforest for its current version.

[jennmattern]

Thanks!

[jennmattern]

Thanks Ed. Will do!

[jennmattern]

Any updates on when the latest version will be available on ThemeForest? I always do these theme upgrades manually, so need access to the files and changelog (for both Flexform and Pinpoint). I see them both with updates in WP but not on ThemeForest yet.

Thanks!

[jennmattern]

Nevermind! It turns out it wasn’t w3 after all. It was an add-on for BBpress (odd because they used to work great together). I figured I’d take one last stab at deleting all plugins and reinstalling them one by one (did that before the final W3 cleanup too). And this one stuck out as the culprit. So it’s all settled now. Three days trying to fix site slowness and related issues with barely any sleep will make even the most obvious solutions slip your mind sometimes. 🙂

[jennmattern]

This reply has been marked as private.