campg2003

Hi,
Our home page is looking different with 4.0– menu squished to the right, smaller title, etc. I want to set up a way to switch between versions so we can easily switch back and forth. Can I:

• Put each version of the theme code in a separate folder
• In style.css change the Theme name line to, say, Responsive340 and Responsive416, respectively.

Can I leave the theme URI alone? Is there anything I have to do to make sure it doesn’t try to update? Anything else?
Thanks.

• This reply was modified 4 years, 8 months ago by campg2003. Reason: Fix formatting

I modified the shortcode because I want to modify which HTML element it uses for the title. A screen reader can jump to headings based on their level. If I have h2 sections on the page and the post titles are also h2, then the screen reader command to jump to the next h2 heading hits every post. If I change the post titles to, say, h3, then the jump to next h2 keystroke jumps past the posts to the next section. I could also change my section titles to h1, but h1 is already used on the page. I was asking about the controlling CSS rule because I did not expect a change, so must have missed something.
Adding the ability to specify the post title tag makes the shortcode a bit more flexible.
Thanks.
Gary

Hi Ryan,

Thanks for letting me know of your interest. I just merged the API V3 fixes to master a couple of days ago– it is V1.1.5 I think. (It also adds the esv_ifpassage shortcode, but that is only useful if you are using passage names.)

Gary

Okay, I found out it was a coding error, two actually, but I had single quotes around the query parm, which I think is why it wasn’t working. Glad I added the URL to the debug output before I tried to ask Crossway about it!

Thanks.

Gary

Hi,

I updated to the V3 API and it’s been working fine for the past few months. However, this week I tried to access a scripture and in the returned response all of the fields except query were empty. Here is the JSON returned for phi 2:4-5:
{“query”:”‘phil 2:4-5′”,”canonical”:””,”parsed”:[],”passage_meta”:[],”passages”:[]}

When I request this from the API V3 page “demo”, the correct information is returned. This seems really odd to me because I am getting a response and a status code of 200. So it is getting my request, it understands what I’m looking for, and it is successfully returning a response, but it isn’t returning the content.

Any idea what’s happening?

Thanks.

Gary

Oh, I should have mentioned that the link is to a patch to your 1.3.5 version.

I tried using a local URL, but I get a 403 forbidden error. I made a local version that works for me. I’m not that familiar with PHP or writing WordPress, so please let me know if there are any poor practices.

Thanks.