nothing is safe to assume

Get specific post metadata custom field:

get_post_meta($post->ID, 'arg', true);

Thanks

sjc999:

get_post_meta($post->ID, 'arg', true);

is not a php function, it's a WordPress function

do_shortcode

in post/page items/footer I use:

<?php if (! is_front_page()) ....
(! is_page(2750))....
(is_page(2750)).....

Optionally; why not have a build for php usage that does not go through wordpress.org?

The people using this theme with php customizations trust the theme now.

make it donation based, gold members

Originally Posted by awcguy

Optionally; why not have a build for php usage that does not go through wordpress.org?

The people using this theme with php customizations trust the theme now.

make it donation based, gold members

We are looking at the idea of having a "premium" version of Atahualpa but there is no time frame set for that.

If possible, write external css and js to files instead of using a query string (?bfa_ata_file=css and ?bfa_ata_file=js) to get rid of partially encrypted errors on SSL pages in Chrome (rex X-ed padlock), Firefox, and IE.

What did not work:
Detecting protocol with PHP (or JavaScript) and using it in the echo statement with the domain name.
Using // syntax for the protocol.
Making sure there were no instances of http:// in CSS options or in the js.php file; $homeURL was reported correctly.
Removing the JS options from the header image.

The links displayed correctly in View Source as https://domain.com/?bfa_ata_file=x, but Chrome (Developer Tools/Console) reported that the pages ran insecure content from http://domain.com/?bfa_ata_file=x not https://...

What worked:
Writing the generated css and js to new files and referencing them in header.php and functions.php instead of the dynamic files.

It takes a little time to write the css and js to files if changed, but at least I can keep using Atahualpa with this site.

Did any of these suggestions make it into a release yet?

I just went through the release announcements from 3.6.8 to 3.7.2 and can't see anything about this stuff.

Thanks,

Mark

These requests are for the next major release of Atahualpa, the releases from 3.6.8 to 3.7.3 have been bug fix's

Originally Posted by juggledad

These requests are for the next major release of Atahualpa, the releases from 3.6.8 to 3.7.3 have been bug fix's

Thanks for the update - I guess that's a change of plan cos the thread was posted asking what people wanted in 3.6.8, which makes sense since while technically these aren't bugs, they are needed to help us get round something that was working and now isn't.

So, when might we expect this lost functionality to be restored (at least in part) through suggestions like support for do_shortcode?

I really could do with that ASAP! (since June 2011)

Mark