If the theme used the built in Custom Header option, I would use that.
If it does not, then hit up the theme author.
Thanks for the feedback.
I am not sure what “Custom Header Option” means, but this issue is in regard to installing a theme on a network of sites (Multi-User) where there is only ONE theme folder that serves all the various sites.
As a result, any banner image in that theme folder gets used for ALL of the sites, which is not appropriate if one is using a custom banner image that may include the site name or specific art.
In Altahualpa particularly the theme grabs all images from the themes image folder to use as banner images and there seems to be no way to specify a unique image folder for each site.
The Network Site capability of WorgPress is very powerful and adds much needed capability. Now the themes will need to have implementation based on this new structure.
Thanks again and I will post at the BFA forum for an answer or solution. Perhaps there is a plug-in to allow for unique banner images per specific network site install?
AK
but this issue is in regard to installing a theme on a network of sites (Multi-User) where there is only ONE theme folder that serves all the various sites.
Ah, a point of clarification.
Any per-site theme options (which, IIRC, Altahualpa has a lot of), remain PER SITE even in a network. You have to hard-code anything you want to be on ALL sites into the theme itself UNLESS the theme has written a way to set defaults for ALL sites in a network.
So … yes, when you see any banner image being available for any site, that’s exactly what’s SUPPOSED to happen in that situation. Talk to the BFA guys, this is on them. If they uploaded the images to the wp-content/blogs.dir/#/files location, like 2010 does, then the images would be PER site.
Ah, a point of clarification.
Any per-site theme options (which, IIRC, Altahualpa has a lot of), remain PER SITE even in a network.
Thanks for the assistance attempt.
Oddly enough this is exactly what does NOT happen with the banner image(s) because Altahualpa uses a GLOBAL, single banner image folder for ALL sites installed on the network.
In other words, even as many unique characteristics can be accessed and changed per site, apparently the header / banner images are in one bulk folder and affect ALL sites in the network.
This is just the opposite of what one would expect if one is customizing parameters for specific sites within a network of sites. All other settings affect the specific site EXCEPT banner image(s).
What Altahualpa needs to add (so it seems) is a way to specify the banner image folder on a per site basis so that each site can be directed to access a specific banner image folder.
This would be very useful functionality for Altahualpa in a network setting and some might say that it is critical. Without it, one is relegated to using the same images for all sites. Not good.
AK
Further specific clarification regarding my own scenario.
I have a network of sites and Altahualpa as my theme for several sites. I created a banner image for one of the sites and ULed it to the image folder where Altahualpa grabs it’s banner images from.
At the same time I had to remove the Altahualpa default images from that folder (I actually just renamed the folder “images_archive”. Now my initial site looks great with the original banner image.
The problem now arises with the SECOND site that uses Altahualpa in that there is only ONE “image” folder that Altahualpa accesses for ALL banner images on all sites using Altahualpa.
OOPS., not good. In addition, there is NO way to turn OFF using a header / banner image (that I could find?) and so my second site is loading the FIRST sites unique banner image. Oops again.
The workaround that I had to use temporarily is to tell Altahualpa that for my second site, the banner image height is “0” or zero, which causes no image to be displayed. Not a great solution.
The best way to solve this is to;
A. Be able to turn the banner image on or off in Altahualpa
B. Enable specifying a unique banner image folder for EACH site in a network within that site’s Altahualpa settings.
Am very curious as to what other users are doing in a network setting for Altahualpa banners. Perhaps they are using the Logo feature for the unique per site banner image instead?
AK
What Altahualpa needs to add (so it seems) is a way to specify the banner image folder on a per site basis so that each site can be directed to access a specific banner image folder.
I’d concur and the theme author is the one who needs to fix this.
There is a fix for this. Take a look at this instruction page:
http://alantait.net/2011/06/09/atahualpa-easy-header-fix/
It uses the WP Image Uploader to put the header, logo and favicon images in the standard WP image locations, and server them from there on a per site basis.
A number of post on the BytesForAll forum say this is working perfectly, even on one WP install with dozens of sites!
It also works with the the WP Multi Network plugin I have read.
The main page (mainly links to history pages) for this fix is:
http://alantait.net/atahualpa/
The Download Page (only 22KB’s!) for this Patch or Fix is at:
http://alantait.net/atahualpa/atahualpa-easy-header-fix-downloads/
It took me 5 minutes to install this on my test platform (your time may very) and less than an hour to configure it (just the Patch or Fix, not Atahualpa itself).
If you try this on a production site please post your results.
OK, after looking into various work-arounds we have decided to scrap using Atahualpa in favor of a theme that is fully supported for multi-site networks.
Our feeling is that we would prefer a theme that is in production with full capability intact without using patches or fixes. Atahualpa seems fine for a single web site though.
For our network of sites we do not feel confident in using this theme until the matter of unique headers for individual sites is addressed properly. Many other themes handle this easily.
Thanks for the suggestions though.
@ashokankid
Would you like a fork of the Atahualpa Theme? Read on!
I think there are many (like me) that echo your last thoughts. Nonetheless, even with the patch or fix, Atahualpa is still one of or perhaps the best theme for MultiSite installs and Multi Networks.
We have it working, in production, on a network of more than 3 dozen sites.
In fact it works so well, a few people are talking about a fork of Atahualpa, humorously referred to as “To Code!”
If you are interested in this, perhaps you would add a comment about a problem or feature you would like to see resolved/added to “To Code”.
http://alantait.net/2011/07/31/to-code-the-new-atahualpa-wordpress-theme/
Let me stress, EVERY ISSUE addressed in this thread (as well as a number that are not) are already resolved in the “To Code” Fork and it is running on a number of network sites.
This Mature Code was offered to the developers of Atahualpa for each of the last seven releases. It has not only been rejected, most threads about it on their “support” forum have been deleted.
Recently the support forum was changed from free to a paid basis.
The main developer is working on a new PAID Theme. Since the beta of the paid theme was released, Atahualpa has not been actively developed. In fact a number of newer releases (problem fixes) have actually lost features.
These are all reasons to support the “To Code” Fork or we all may be shelling out 160 bucks for paid “Atahualpa Like” Theme.
Just to set the record straight, the Atahualpa support forums have always been open to anyone who registered. Due to an avalanche of spam, because of the forums high ranking, the theme author made a change so that only members who had donated would be allowed to post, but everyone was and is allowed to view it.
The theme author has made some changes to the forum that seems to be keeping spammers at bay and he has once again opened the forums to everyone.
The ‘lost’ features that ‘VeGenesist’ refers to were items that were removed due to changes in WordPress requirements for theme approval. No one wanted them gone, but it was remove them or the theme would have been dead.
As for the ‘7’ releases this code has been ‘offered’ for, there have only been 2 releases since this ‘code’ was first offered for release 3.6.1 – versions 3.6.4 and 3.6.7, 3.6.2, 3.6.3, 3.6.5 and 3.6.6 were never released!
And lastly, to my knowledge, no threads that address this ‘code’ have been removed from the Atahualpa forums.
Since this thread has derailed, and is specific to one theme that has its own support forum, I’m closing it.
