Will Brownsberger

This issue is resolved in version 2.3.5 (which has been published today). Advanced searches will reload from the search log correctly across all upgrades subsequent to this one. Advanced searches logged before this upgrade will not load correctly, but there is no risk of data loss: One need only re-enter the search terms.

BigBigL, sorry I didn’t see this question in a timely way — not sure how I missed it.

I like what you are doing on your site.

Short codes should work fine in the Front Page Text Widget and elsewhere if you add that line that you identified in the instructions above. That’s a great way to use the Front Page Text Widget.

I can’t diagnose your problem with the information I have so far, but feel to supply more — my direct email is [email protected]. Please do feel free to ping me directly if you’d like.

This was cleaned up in 2.0. The extra lines never had an impact (other than weight), but they have been eliminated.

This issue was fixed in 2.2.3.

I have posted an upgrade, version 2.2.2.1, which should make the autoload issue OK back to PHP version 5.1.2 — other issues might arise for versions that old, but this issue should be eliminated. The spl_autoload_register function dates from PHP 5.1.2., but the plugin was using an additional parameter that was introduced in 5.3.0. That parameter dictated that the loader be prepended to the upload queue instead of appended. This was unnecessary and I removed it in the version 2.2.2.1 of the plugin.

My production site using this plugin runs PHP 5.3.19 and my development site runs PHP 5.5.9-1ubuntu4.9, so any PHP version in this range should be OK for the plugin. WordPress requires PHP version 5.2.4 or greater and recommendeds PHP 5.4 or greater.

thank you for identifying this issue. The plugin does require the php class autoloader. I will confirm the earliest php version that works and add appropriate documentation.

This issue is fully addressed by the new release (2.2.1). The internals of the download process have been rewritten to minimize memory use and database packet size.

P.S. Not sure what you are thinking, but if you want a home page without a header, you may be able to achieve the look you want using the main Responsive Tabs front page which is very flexible.

Set customize > static front page > your latest posts and then go to customize > front page highlight and remove all content from there.

Hi John,

Responsive tabs does honor static front page settings.

If you go to customize > static front page > a static page, you can select any page you choose as your front page.

That front page will display using the template you choose for it — you will see when you edit your page that you have two template options for pages in Responsive Tab: Default (with a sidebar) or Full Width (without a sidebar).

I’m marking this question as resolved, but please hit me back if I’m missing your question.

/w.

Glad you found this fix for your site. When we next release we’ll see if there is a way to accommodate this special naming convention without disrupting the more routine formatting. If you want to send me the URL to your site, I’ll take a look at so that I can get it on the do list. You can send by email at [email protected] if you prefer.

Yikes. That is surprising. It appears to be some kind of glitch in the subversion distribution process.

I did a diff check and the only the differences between the top and bottom halves are the version and wording of the description. They are otherwise identical. So, the the duplication does not affect site behavior.

I deleted all below the following lines (and including those lines) in a test and it works fine. Take care not go above those lines and to delete all those lines. Start with the /*.

Our next release is several months away — planning to add infinite scroll — but we may do something sooner if we identify any glitches that affect functionality.

Thank you for pointing this out.

/*
Theme Name: Responsive Tabs
Theme URI: 	https://responsive-tabs-theme-for-wp.com
<<<<<<< HEAD
Author URI:
=======
>>>>>>> 1e0c8c25219b1ccadb47bdd7652ff0d86b6c1a83

Thank you for the question. Glad to know that you are interested in that project.

All strings are set up with proper internationalization with pointers to text domain ‘responsive-tabs’, so that if you are interested in translating, you’ll be ready to go with that project. But you are correct, we have not actually created the language file. We were guided by the standards at this link: https://codex.www.ads-software.com/I18n_for_WordPress_Developers

This problem does appear to have resolved itself without any action by me or by my web hosting company. I’ll start a new thread if it reappears. There are a number of threads on this problem and most of what appears in them is probably bad advice — people thinking they solved the problem when it actually solved itself.

Additionally, I have run a malware check on Sucuri, which comes up clean.

The error appears only for logged-in users.

Which of several issues mentioned is fixed in the next release?