|
Changelog 3.1.8/3.1.9 -> 3.2
Atahualpa 3.2 is available here http://wordpress.bytesforall.com/?p=67
Changelog 3.1.8/3.1.9 -> 3.2 (See http://forum.bytesforall.com/showthread.php?t=199 for fixes and improvements that didn't make it into 3.2)
|
thank you for considering Tabbed Widgets. Not only is it a great option, but I've been contemplating adding it and didn't want to bother un-uglying it, so this is good. Thanks!:p
|
Do you think it might be possible to have more widgetized (side)bars and an even more flexible layout (e.g. full width bars above first post and under last post, or sth. allowing category bars, i.e. vertical or horizontal bars that display posts from certain categories...)? Atahualpa rocks!-)
|
Adding more widget areas shouldn't be too hard, I'll add that on my to do list, not for the next version though
|
would it be possible to offload the css from the widget options screen into a separate css file? the <head> section has become so long. does that make sense?
otherwise, this is fantastic! hands down the best wordpress theme i've ever seen. :) |
You can cut and paste the inline CSS to the bottom of style.css after you're done with the customizations.
I know what you mean and I had it like that with a dynamic style.css.php but that had its own problems. |
hmm, does that create any conflicts/redundacies if I make future edits through the options panel, or do I just need to make sure I cut and paste the inline CSS into style.css each time I make changes in the options panel?
|
Sorry it was a bit misleading the way I described it
You should copy the inline CSS section in your site's header area (the CSS between <head> and </head>) by looking into the source code of the rendered page (when viewing it in the browser). After you pasted that to the bottom of style.css, you could delete the long dynamic css portion from header.php. |
awesome. thank you very much!
|
Again, as a complete newbie, I'm assuming from what you say above that the feedburner issue is NOT yet resolved in 3.8.1 or 3.8.9, correct? Is this something that will be fixed in 3.2?
Thanks so much. |
The google/feedburner issue is not resolved in 3.1.8/3.1.9. It will be in 3.2 which I plan to release within a few days. I'll just do the Feedburner issue and the new languages for 3.2 so it won't be delayed. I am halfway through with both.
|
Thank you. I'll check back at the end of the week.
|
Hi
Great to see there is an update available, but can you clarify on these points, please:- 1) If I download 3.2, will I first have to save or in any way protect my existing settings on 3.1.9, or will everything just install without a fuss? 2) My existing (first installation of this theme) is in a folder called "atahualpa", rather than "atahualpa3" - will this be a problem for me? Thanks, Matt |
The settings that you made through "Atahualpa Theme Options" are saved in the Wordpress database and would not be affected when you overwrite the existing theme version with the new one. Any manual code changes you may have made in the theme files WOULD be affected IF you overwrite the existing theme files.
1) Settings through "Atahualpa Theme Options" -> won't be overwritten no matter what you upload and where 2) Manual theme file edits: Will be overwritten if you upload into the same directory ("atahualpa" or "atahualpa3" or whatever) The /atahualpa/ vs /atahualpa3/ issue started when Wordpress changed my uploaded /atahualpa3/ to /atahualpa/ which I wasn't aware of until recently. My intention was to have the 3.x series of Atahualpa in /atahualpa3/ so users of Atahualpa 2.x could keep using 2.x and try out 3.x at the same time. That plan didn't work out as expected. From the next version 3.2.1 on either I will start using /atahualpa/ or Wordpress will start using /atahualpa3/ to stop the confusion. You can upload the new version as /atahualpa/, which would overwrite the existing /atahualpa/ on your web server. Or you upload as /atahualpa3/. Then you would have both 3.1x. and 3.2 online and could switch between them at Site Admin -> Appearance -> Themes. Both theme versions would have their own theme files, but use the same settings in the Wordpress database. Changing a setting in one theme version through "Atahualpa Theme Option" would affect both versions. There should be no hard coded /atahualpa3/ or /atahualpa/ in the theme files. You should be able to name the directory any way you want. |
Upgrade went smoothly, just had to change the title tag for my ttf-titles (as expected), everything else works as it should... thanks again, Flynn, well-done!
|
Flynn,
Will all of the customization that I have on my blog remain if I upgrade from 3.1.9 to 3.2? I don't want to lose any of my sidebar widgets (or more precisely the code within them). |
I should have read the thread before posting.
But I am having problems with the upgrade. I'll be back with details. |
Duh I realized that I was activating the old atahualpa theme. When I activated the new one, it worked BUT the background color of my header area changed to white. I went into the styling options for the header and the correct color code was still there but apparently it's now being overridden by something. I switched back to 3.1.9.
|
Have you hard coded any color into the theme files? Another possibility would be that you took away something and now a white color is "shining through" from the backgound. I would have to see to find the error.
|
I would like to return to my "more widgetized areas" suggestion which you said might make it into the theme in a future version. Having thought a little bit about that, how about an addition to the layout admin page offering a 3x3 cells layout box for everything that goes underneath the Category Menu Bar? Ideally, each of these cells should be able to carry either widgets or php code.
Usually the content would go into the middle cell of the top row or the second row (providing the possibility to use e.g. a carousel plugin in the middle cell of the top row. The Revolution/Hemingway-famous 3-columned bottom content might be put into the three bottom line cells, and e.g. a complex category navigation may be put in the first cell of the middle row. In other words, a complex magazine layout could easily be realized... The thing is that ideally cells should be "mergeable" (meaning that e.g. the carousel can go full width)... - Maybe a choice of 5-7 cell arrangement sets on the layout admin page (i.e. one with a full width top row, one with a two-cell first row [first and second OR second and third cell of the top row merged] etc.) might be the most user-friendly approach? - Oh dear, this reads quite complicated... and I doubt that this is where you want to go with this magnificent theme... ...and another thing in the context of the magazine aspects: besides "full post" and "excerpt", a third post display choice ("title only") might come in handy... Please forgive my impertinence (if you think it is that...-), I just want to show my enthusiasm for your work, and my interest in its further development... Greets from Germany! |
No I didn't hard code anything into the themes files. In my current version (3.1.9) I have the following set:
In (Atahualpa Theme Options ->Header->Blog Title) I have this bit of styling: background-color:#EDF2EC; When I switched 3.2 the Blog Title background turned white yet the styling code remains. So something is overriding it. |
Matthias, those are good suggestions that I will keep in mind. Especially the title only option is something I had not thought about yet, and I see where you're getting at with the mergeable cells. There's still some things on the to-do list though that I need to get out of the way first. I will also have to find a way to cut down on the time that this forum consumes. I see that you've gone far with the customizations compared to others. If you see a question that you would be able to answer please don't hesitate to do so :)
|
I'll try... promised!
Henry, what's your URL?-) |
is the styles.css.php not needed anymore? at some point I can't find it in the archive ... but it is in the "old" directory at the server ...
|
styles.css.php is gone, the dynamic CSS is in header.php now.
|
| All times are GMT -6. The time now is 05:12 AM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.