http://oneworldnow.net/ is my website and on each Atahualpa upgrade I must manually:

1. load header pictures
2. favicon
3. 'tpg get posts'-style.css file

Is there a way that this can be always standard and not touched by Atahualpa updates?

Thanks in advance.

yes there is, take a look thru the forums and you will find some solutions.

Thanks for making the theme accommodate the favicon and header!

I could not, however, fix the problem with the tpg plugin. Whenever Atahualpa is updated somehow that file is changed. How can I keep this from changing?

Cheers!

What is changing?

I have to replace that file on each upgrade of the theme. I use tpg get posts to remove the author info on the main page.

what file? in the plugin folder? theme folder?

you have to realize, I've never heard of the plugin so you are the expert when it comes to this plugin.

in the plugin folder: tpg-get-posts.php

the strange thing is this is not in the atahualpa folder,but nonetheless is destroyed with each Atahualpa update.

Here is the code from it in case this helps:

/*
* Styling for the tpg-get-post plugin
* all items prefaced with tgp (for tpg-get-posts)
*/
/* styling for posts*/
/* wrapper for all posts pulled by shortcode */
#tpg-get-posts{clear:both;}

/* wrapper for individual post */
.tpg-get-posts-post{clear:both;}
/* class for title*/
.tpg-title-class{
margin-top:1em !important;
}
/* class of by-line*/
.tpg-byline-class {
margin-left:1em;
font-size:small;
}

/* class for content*/
.tpg-get-posts-thumbnail{clear:both;}
.tpg-content-class{}
.tpg-thumbnail-class{}
.tpg--excerpt-class{clear:both;}
/* class for metadata*/
.tpg-metadata-class {
margin-left:2em;
font-size:x-small;
}
.tpg-ul-class {}
/*class for <hr> after list */
.tpg-get-post-li-hr {display:none}

.tpg-byline-class {
display: none !important;
}


I honestly don't know why it is destroyed at each update of the theme.

updating the theme should not touch a plugin's file...unless you are putting the plugin's css file in the theme folder - which you shouldn't

one other thought, it could possibly be something your host is doing - a slight chance, but maybe you should ask them about this.

thanks so much. i will look into this.

thanks so much!

go read the first line of the plugin's styling section.