BytesForAll WordPress Themes

This 3.7.1 release fixes one fatal bug that occurs when you edit a .php theme file on right on the web server, see also http://forum.bytesforall.com/showthread.php?t=15572

Download Atahualpa 3.7.1 at wordpress.org

Changelog 3.7.1:

- Editing a .php theme file (such as functions.php) right on the web server, through WP Admin -> Appearance -> Editor, would break the theme

The following download link below is meant for downloading an “older Atahualpa, in the future”, in case you need it sometime, or if the new version has not been published yet at wordpress.org :

October 6th, 2011 • Leave a comment

Yet another update. This should be the last for a few weeks. 3.7.0 contains a few security improvements as requested by WordPress

Download Atahualpa 3.7.0 at wordpress.org

Changelog 3.7.0:

- Escaped several user input fields, mainly search form inputs

The following download link below is meant for downloading an “older Atahualpa, in the future”, in case you need it sometime:

October 4th, 2011 • Comments (3)

Sorry for 2 updates in 2 days. Atahualpa 3.6.9 has only 1 bugfix, not critical but annoying:

- Between page reloads on the theme option pages, the active menu tab was not remembered, you always had to click the tab you previously were on, again

October 4th, 2011 • Leave a comment

This release has 1 security fix and a couple other bug fixes and improvements.

Changelog 3.6.8:

- esc_js added to get_search_query, XSS vulnerability
- issue with css.php: http://forum.bytesforall.com/showthread.php?t=14143
- Page titles doubled & ‘title’ attrbute missing post title: http://forum.bytesforall.com/showthread.php?t=14718
- PHP errors when adding widget areas: http://forum.bytesforall.com/showthread.php?t=14160
- Site Title appended after the ‘WordPress SEO by Yoast’ title: http://forum.bytesforall.com/showthread.php?t=14816
- PHP was still being advertised as being available at “Edit POST/PAGE info items”
- CSS print style would not work right in some cases
- removed proprietary function “bfa_escape”
- replaced proprietary “Tabs” javascript with jQuery -> 1 file less to be loaded in the backend
- The internal CSS & JS files for the Ata admin area are now added through WP
- After you imported a style, you had to reload the amdin area manually to see the new values. Now the page reloads automatically after a style was imported.
- Removed several PHP Notices in the included widgets Recent Posts/Popular Posts/Popular in Category
- Changed the page slug (see browser URL field) of the Atahualpa admin area from “functions.php” to “atahualpa-options”
- Replaced with ‘/wp-content/themes/atahualpa’ in the CSS image paths of all 5 included styles.

Issues found by the theme check plugin:
- Both DOS and UNIX style line endings were found in the file bfa_theme_options.php
- text domain missing at some places in functions.php, comments.php, legacy.comments.php and comments-paged.php

Just in case you wondered, Atahualpa – the #1 downloaded theme on wordpress.org – is alive and will keep getting updated. The next update should be in a couple weeks, or if required, in a couple days. Sorry that this update took so long.

October 2nd, 2011 • Comments (2)

UPDATE:  Atahualpa 3.6.7 released.

In 3.6.7:

• custom widget areas work again, same usage
• plus 2 more bugfixes (1 Typo and this )

In 3.6.6:

This version has 2 big changes due to changes in the requirements for themes listed at wordpress.org (no file operations, no custom PHP code):

• No file operations: Import settings by copying the (content of) the settings file and pasting it into the Atahualpa Theme options – instead of being able to directly upload the settings file. Not a big hassle I think. You probably won’t be importing styles all the time.
• No custom PHP code anymore: After the “Eval” function was not permitted anymore in themes, the alternative “stream wrappers” caused issues on all hosts where Suhosin was installed. The remaining option “temp. files” isn’t an option either because that requires file operations again. Atahualpa was one of few themes, if not the only one, to offer the ability to add custom PHP through theme options. This is not possible anymore in themes listed on wordpress.org. There might be workarounds or even alternative theme options in the near future, here or on the forum

Bugfixes:

See all 8 Bugfixes of Paul, at http://forum.bytesforall.com/forumdisplay.php?f=12, everthing with 364-XX
and a few more by me.

May 11th, 2011 • Comments (52)

ThemeFrame Release Candidate available at ThemeFrame.com 

Get ThemeFrame at a reduced price while it is in Release Candidate stage.  The price will increase in steps as ThemeFrame improves, and will reach its regular price once the RC stage is over. Existing users aren’t affected by any price increases, you get a lifetime license, no recurring payments. The earlier you get ThemeFrame the more you will save.

ThemeFrame lets you create WordPress themes in a visual environment that runs in your browser, on your desktop computer. ThemeFrame is not a theme itself (like “Premium WordPress Themes” usually are), but a program that CREATES WP themes:

Check out the ThemeFrame screenshots, docs, videos, forum at themeframe.com

March 11th, 2011 • Comments (20)

 Download Atahualpa 3.6.4 here

This version is in the review queue at wordpress.org but not listed yet

- BUGFIX 361-01: meta tags not appearing in generated source
- BUGFIX 361-02: Tab order on comment form incorrect when user is not logged in
- BUGFIX 361-03: Allow Tag widget links to use Atahualpa widget link styling.
- BUGFIX 361-04: Allow Custom Menu widget links to use same styling as Pages widget.

See also http://forum.bytesforall.com/forumdisplay.php?f=12

2 new options:

• “Style & configure LAYOUT” -> “Emulate IE7″. It defaults to ‘No’ and will only generate the line <meta http-equiv=”X-UA-Compatible” content=”IE=EmulateIE7″ /> when set to ‘Yes’
• “Header Image” -> “Overlay Header Image”

Check out the BytesForAll Forum to discuss Atahualpa with other users

January 31st, 2011 • Comments (37)

 Download Atahualpa 3.6.1 here

This version is in the review queue at wordpress.org but not listed yet

• Added ‘global $templateURI,  $homeURL’ to header.php
• Added ‘$templateURI’ to css.php
• Replaced ‘caller_get_posts’ (deprecated in WP 3.1) with new function ‘ignore_sticky_posts’ in footer.php line 35
• Removed unnecessary ‘return’ from bottom of functions/bfa_meta_tags.php
• Removed repetitive code from css.php
• Removed ‘canoncial URL’ and RSS feed URLs from html HEAD, WP is adding these now
• Moved ‘ddroundies’ JS code and wp_enqueue(jquery) from header.php to functions.php
• Replaced bloginfo( ‘url’ ) with echo home_url() in functions/bfa_header_config.php line 276
• Replaced get_bloginfo(‘text_direction’) with is_rtl() in functions/bfa_body_class.php
• Renamed GPL.txt to license.txt
• Permalink for posts without title: Instead of the title the word ‘Permalink’ is displayed and linked to the full post.
• Option “Show XHTML tags?” works again but is below the textarea now (it was above). This is more in line with the new WP comment_form() (using the new parameter ‘comment_notes_after’), instead of making something hackish to keep it above the form.
• Comment submit button is jQuery-enhanced again (Highlight on Hover)
• Comment form labels (“Name”, “Email”, “Website”) are on the right side of their input fields again.
• Added sample content to sidebar ‘right-inner’
• Added check for bfa_get_options in functions/bfa_get_options.php – [url]http://forum.bytesforall.com/showthread.php?t=12111[/url]
• Edited style.css from ’0-6 sidebars’ to ’0-4 sidebars’.

(P.S.: Download number was reset after server move)

Check out the BytesForAll Forum to discuss Atahualpa with other users

January 10th, 2011 • Comments (22)

WordPress.org has changed the submission process for themes and also added quite a list of new requirements. Also, themes aren’t reviewed by Automattic employees anymore but by volunteers, i.e. theme and plugin authors.

This has various implications, one being that providing backwards compatibility with older WP versions has become an impossible task because the sheer existence of some older functions (pre WP3) will trigger an alert of the automated submission script at WordPress.org and the theme will be denied automatically.

So from now on Atahualpa will be ready for the current and the past WP version, but not for older WP versions. WordPress clearly does not want theme authors to provide too much backwards compatibility and rather see people upgrading to the new WP version all the time.

Consequently this 3.6 version has some old code removed and will very likely break with anything older than WP 3.0! So don’t use Atahualpa 3.6 if your WP version is older than 3.0!

One rather big change in 3.6 is that the PHP eval function that was used for custom code inserts (all the text areas in the Atahualpa admin where you can put PHP code) is now replaced by PHP stream wrappers. (“Eval” is also not allowed anymore).

Other changes:

• fixed many PHP notices
• replaced many deprecated WordPress functions with their new equivalents
• dozens of little changes requested by the new WordPress.org submission script, and by reviewers

Right now 3.6 is still in the queue3.6 is now available at WordPress.org but you can also download it here:

(P.S.: Download number was reset after server move)

Check out the BytesForAll Forum to discuss Atahualpa with other users

ADDED Jan 6 2011: A new version will follow within 2 weeks max to fix the issues posted below in the comments, and on the forum. There were so many (like 50+) changes in this version due to the new WordPress.org requirements. Now that these changes and fixes are done I can finally focus on user issues again.

ADDED Jan 8 2011: Please see http://forum.bytesforall.com/showthread.php?t=12048 for a fix for issues related to favicons and CSS.

January 4th, 2011 • Comments (29)