Miss the old days where updates consisted of long lengthy step lists on files to edit, lines where to edit.

Hard to sell products like that to the masses though right 😛

Sorry I am just dealing with this now lol

I actually skin my theme versus just getting it, and uploading it to my server and having a site in a can website.

So I am pretty screwed when it comes to updating. Hense why an easy fix with documentation on fixing the bug issue is more ideal for folks like myself, versus the masses that do not edit their theme and simply are told to just reupload the whole theme files to solve the issue.

Is there a fix for this other then simply reuploading whole theme again?

I’ve updated my theme extensively and to have to redo the whole design, css and everything else, would be such a hastle to fix a small bug. Is there some sort of guide or steps to get this glitch sorted out? I don’t want to be skinning a wp theme days before Christmas… Leave it to WP to launch a update right before Christmas too…

Getting tired of this CMS really, tbh.

• This reply was modified 10 years by SaL.

Yea unfortunately that seems what I need to do.

By removing the old theme, that won’t delete my homepage block settings and stuff right? All that is saved via DB correct?

Really sucks all these wicked themes come injected with so much extra code to make it more appealing to the general audience. I understand it increases more sales, but really burdens those who only need the theme for blog site, not ecommerce, buddypress and so on.

I appreciate your support, and the great theme. I will try again this weekend with total reinstall and by adding all my edits in. Which shouldnt be that bad, we only use 2 of the post templates and the css done by you guys was so stellar that getting the look back on the site would be a breeze.

If epic fail again then looks like I need to get in touch with someone to make us a custom theme geared towards our site.

Is there a patch folder from 2.0 to 2.1? Perhaps I need that one first…

This is the process I went to update theme…

Deactivated Revslider, Js Composer, Social Counter

Reuploaded those plugins via FTP overwrite.

Uploaded all patch files (some files were missing like td_api were not in the patch directory, noticed after upload and simply just reuploaded the whole theme folder skipping exisiting files.

I had my managed team revert the server back to last night. Lost a few posts this morning but good thing it’s a holiday and traffic is slow 😉

I would really like to have one of your specialists work with us to get this updated.

Is there any direct contact email I can give you a shout from? I dislike sharing my site name on theme support forums as they tend to be a trolling ground for malicious folks to gather info of certain sites running certain themes and create a database of them for future attacks.

Perhaps an option on the forums is to allow post author to select private post only for admins to see.

Fatal error: Access to undeclared static property: td_global::$all_theme_panels_list in includes/td_config.php on line 2726

OK Cool, I will give that a shot this weekend and get back to you all! Thanks again for the support, it’s greatly appreciated. You guys do a great job and im happy I found you & your theme 😀

Also forgot to mention that we are running version 2.0.

I see the patch2.1_2.2 folder in theme however there are some files in there that I have done edits too.

If I update just the js_composer files would that work with my original installation from July 17th?

I don’t really want to update the theme files unless there is a security risk or simply doesn’t work and by the looks of it, it’s working fine atm. Just having that issue with the page builder glitching in admin.

I have done extensive modifications to the theme so fingers crossed all updated files are documented 😉

Perhaps I need to update the composer files? I haven’t done this since initial theme installation back in July 17th.

Can I simply just download the files and rewrite them in the plugins folder via ftp? I noticed the composer files have edit dates of July 30th so most likely cause of my issue.

I noticed you can exclude categories from homepage blocks (eg: -76)

However I tried this for the tags and received an error.

I did what you suggested and:

array(‘text’ => ‘640 x 280’ , ‘val’ => ‘640 x 280’),

Have this ad type set to only display desktop mode.

Thanks again eh, lovely support, lovely theme.

Ahhh ok, it be nice if auto was fluid though. All you do is set a height or something.

Text ads inline 600w x 280h look pretty spot on, hense why I want to do this. I can do it on my category pages, but I don’t use custom ad locations for that placement, therefore I am able to have the google code work correctly without the custom ad code auto wrap sizes.

Having the ad this size creates more competition from different ad sizes that can fit insize the square.

The content inline auto ad is a 468 banner, and those stopped being good ads once everyone moved onto larger resolutions years ago.

I guess there is no way to set percentage within the val => eh? For example ‘val’ => ‘100% x 280’)

Restored, compared files and found what I did… total brain fart and this is what caused the issue:

‘custom_ad_5’ => ‘custom_ad_6’,
‘custom_ad_5’ => ‘custom_ad_7’,
‘custom_ad_5’ => ‘custom_ad_8’,
‘custom_ad_5’ => ‘custom_ad_9’,
‘custom_ad_5’ => ‘custom_ad_10’

I forgot to change the other numbers lol Totally over looked it last night, was late. Even overlooked it this morning otherwise restoration wouldn’t have taken place 😉

I still receive errors within Custom Page Builder though.

I will capture a screeny next time I see it.

Reverting back to a backup from yesterday.

I checked my error log and these are all the errors we have logged since theme installation:

[18-Jul-2015 02:00:52 UTC] PHP Fatal error: Call to undefined function get_header() in /home/save5478/public_html/wp-content/themes/salv5/index.php on line 6
[19-Jul-2015 14:54:21 UTC] PHP Fatal error: Class ‘td_global’ not found in /home/save5478/public_html/wp-content/themes/salv5/404.php on line 6
[20-Jul-2015 04:59:32 UTC] PHP Fatal error: Call to undefined function get_header() in /home/save5478/public_html/wp-content/themes/salv5/index.php on line 6
[23-Jul-2015 21:37:16 UTC] PHP Fatal error: Call to undefined function get_header() in /home/save5478/public_html/wp-content/themes/salv5/index.php on line 6
[24-Jul-2015 22:59:20 UTC] PHP Fatal error: Call to undefined function get_header() in /home/save5478/public_html/wp-content/themes/salv5/index.php on line 6

I noticed these errors when using the custom page builder. Modifying settings such as responsiveness / design options.

• This reply was modified 11 years by SaL.

Only changes i’ve done to the config file is add the ability of 5 more custom ad spots.

Works perfectly!

Thanks a lot Lucian!

Congrats guys on such an awesome theme!

I added:

‘tag__not_in’=> ‘6725’,

to

‘category_ids’ => ”,
‘category_id’ => ”,
‘tag_slug’ => ”,
‘sort’ => ”,
‘limit’ => ”, /*’limit’ => 5,*/
‘autors_id’ => ”,
‘installed_post_types’ => ”,
‘posts_per_page’ => ”,
‘offset’ => ”,
‘live_filter’ => ”,
‘live_filter_cur_post_id’ => ”, //this is auto generated by the block render ( add_live_filter_atts ) only when it’s needed – it’s the current post id
‘live_filter_cur_post_author’ => ” //auto generated – author_id of current post

Still no luck with having those expired tagged posts being removed from category.

• This reply was modified 11 years by SaL.