etfb

This happened to me too, repeatedly. There was no good reason for it, so after struggling for a while I made the decision to ditch the Sydney theme and move away from aThemes as a whole. I just don’t have any faith that their paid versions will be any less error-prone than their free themes are already well-known to be. Perhaps if they spent a little more effort on testing and proofreading, they would be a better prospect.

Found the source of the problem: my slideshow has over 100 entries, and that comes up against the PHP max_input_vars setting, which defaults to 1000. Counting all the edit fields of every single slide equals more than the limit, so not everything was getting through. I upped the limit in my php.ini and it’s now working.

Suggestion for this plugin’s developer: use a little bit of JavaScript to amalgamate the fields and strip out unused ones. Also, do a quick check of the number of $_POST vars and compare with the setting to warn the user that there may be a problem.

While it’s definitely the Wrong Thing for the developer of this plugin to leave warning messages like that in a released plugin, you can switch off warnings and notices and you should stop seeing the messages anywhere except in your log files.

Excellent advice. Given that your plugin doesn’t work and your website is down, I shall take this dead-in-the-water plugin and stick it where you got your crappy attitude from.

Confirming that the patch definitely fixes the long-standing bug in this plugin relating to the use of the Customizer with domains outside the default. Needs to be rolled in ASAP.

Now hunting down the appropriate settings for the Cart66 incompatibility.

That looks promising. I’m having a similar problem with the Cart66 plugin, which works on one site and not another. The difference between the sites is that the first is using its default domain and the second has a different primary domain. The obvious conclusion is that Domain Mapper does something to make Cart66’s AJAX functionality fail due to the domain being identified inconsistently.

I will use your technique to see if I can fix this. If I can, it would appear that this plugin will need some kind of whitelisting feature to enable other plugins and features to work with it. I’ll report back with my results shortly.

Ron – latest version of everything: WordPress 3.4.1, plugin version 0.5.4.3. I have my WP installation on example.com, and several sites with their primary URLS on foo.com, bar.com and baz.com. Sites like a.example.com, b.example.com and c.example.com all work fine with the customizer, but any site like x.foo.com or y.bar.com does not.

Clearly what’s happening is the Customizer is refusing to see, say, “afoo.example.com” (which is the default name for the site at a.foo.com) as a reasonable alias for a.foo.com, somehow. Somewhere in your code, an alias is being translated too early or too late.

Contact me on [email protected] and I’ll point a couple of different domains at your test site of choice so you can see the problem in action.

Yep, got that version; still doesn’t work.

… Aaaaaand: it still doesn’t work. Bugger. Well, at least I now know who to blame.

Oh, thank the gods! Some pillock over in the #wordpress channel insisted that I must be making this up, but I’ve never once succeeded in getting the Customize feature to work and, sure enough, I use the Domain Mapping pluging — which I can’t switch off because it would disable all my sites! I’ll try the dev version and see if it’s fixed.

The suggested changes are merely what PHP assumes, and of course PHP assumes wrongly. The correct changes should be WP_PLUGIN_URL and WP_PLUGIN_DIR, but if you’re using a very old version of PHP then all bets are off.

Also, all references to $this->options[…] need an @ sign before them. Please test your plugin with debugging switched on and the error_reporting(E_ALL|E_STRICT) option to make sure you don’t miss things!

I’m guessing that the complete lack of any [expletive deleted] documentation at all is the reason that this user and many others are having trouble with this waste of a plugin. Get some clue, will you? You should be ashamed of yourself, Matt.

So you’re saying you got it working by using a totally different plugin instead of this one? Yep, that seems to be the best solution. This one is dead.

If it doesn’t work without specific settings, and the installation instructions say it does, then the installation instructions are wrong and the plugin is broken.

NOT recommended.