kyle-skrinak

Yes, they support imagick php extension. Instructions here: https://wiki.dreamhost.com/ImageMagick_and_imagick_php_module_on_shared_hosting

Same here. Fancybox js uses an unsupported call to browser. Disabling for now.

As I stated, I believe the core issue is the original site designer’s implementation of a flawed data model. The client was uninterested in a redesign, so the project closed without action.

Yep, it’s fixed. Thanks!

Joe,

It wasn’t the problem with OptionTree, but rather how a theme my client purchased “integrates” the OT functionality.

The good news is that the fix was easy in my case. Go to the User Profile view for the account you use for editing. Below the “Password” section is the OptionTree setting, “Show Settings and Docs” After I enabled that, I was able to see the OptionTree settings menu from the main admin menu, with full access to my settings.

Hope that helps!

So I scrambled, re-entered, completed the draft site, and migrated it to a public server for customer review. However, the same thing just happened: option-tree configuration for my theme is gone. Empty settings.

It seems there’s a bevy of plugins that offer similar functionality. However, as I prefer to do so manually, I’m not pursuing this any further right now. (It was curiosity, not necessity, that had me looking.) I’d love to hear, however, if you find a plugin that does a good job replicating this feature.

OK, it’s not missing. WordPress.com and WordPress.org are two very different beasts. Since I prefer to self-host, this isn’t in “core” as one might think if not paying close attention to the platform.

I’m experiencing the same issue. I’ve tried the myriad of things to try:

• Empty Browser Cache
• Increase php memory
• Disabling all plugins
• Confirmed my wp-settings.php and wp-config.php include all changes from the 3.0.3 base

Is this because I’ve migrated the database forward since 2.x?

If by “bug” we mean that, when using safari and WP 2.3.3, that WP strips all paragraph returns out of either the “visual” or “code” panels when posting, then yes, I can replicate the problem. Commenting out the code, as suggested above, does not fix the problem.

To add insult to injury, if I copy text from MS Word to Safari, Safari will faithfully place all RTF formatting into the post field. Thereby killing the theme with arbitrary text formatting code. I file it under “thanks for nothing.”

I don’t have either problem when using camino. I’ve advise my client to switch to camino but safari support would be nice, of course.

I am having the same problem, same verification procedures.