Oliver Juhas | WebMan Design

Hi,

Please note that this plugin is for theme developers only. As it is closely tied to release of my new theme (which uses the plugin) I would rather not disclosed any detailed info. Anyway, you will be able to find a documentation on https://support.webmandesign.eu/forums/forum/webman-amplifier/. I will constantly create a new topics for developers on how to use the plugin.

You have to define the custom metaboxes and meta fields. Please go through the whole webman-amplifier-setup.php file and read the code comments on how to enable and use the plugin features.

Also, please direct all your future questions on https://support.webmandesign.eu/forums/forum/webman-amplifier/ support forum.

Thank you for understanding.

Regards,

Oliver

Hi,

Sorry for such a late reply. I haven’t noticed any support request.

Yes, the plugin should be released this week. The release will be accompanied with a new theme. Please check the https://www.webmandesign.eu for more info.

Regards,

Oliver

Hi Matt,

Thanks for the suggestion. This have actually pushed me to investigate the WordPress core in more details as I presume there are more plugins registering sidebars than WooSidebars ??

So, better solution would be to tweek the default register_sidebar() args in the WordPress core, which is possible via register_sidebar action hook. So my problem is sorted (although I’ve chosen to hook onto dynamic_sidebar_params filter instead).

Regards,

Oliver

Hi,

Actually, you are right. It’s working fine now… though I haven’t applied any changes/fixes…

Consider this as resolved.

Regards,

Oliver

https://core.trac.www.ads-software.com/ticket/24334

Thanks for pointing out to the ticket.

Thanks for reply.

I have WordPress Network enabled and checked on Twenty Thirteen theme. Only plugin enabled is WordPress Beta Tester (network enabled).

I’ll try on WP singlesite and also to install on Ubuntu to see if it works there.

Will let you know how that goes.

Hi,

Not sure if I am doing something wrong or the WP3.6 (beta 3) doesn’t support the feature, but removing certain post formats doesn’t work:

remove_theme_support( 'post-formats', array( 'image', 'chat', 'aside' ) );

…neither…

remove_theme_support( 'structured-post-formats', array( 'image', 'chat', 'aside' ) );

Hoping this will work in later versions of WP… Or are we left with hiding the post format selectors with CSS in admin?

Thank you for the answer.

The code was created by me and is not in any online repository to see. But I can explain what it does:

• edit_form_after_title hook – I output UL list of tabbed interface here and open the first tab content DIV
• edit_form_after_editor hook – I close the first tab content DIV and output the other content DIVs

The first content DIV is always a visual editor. But as you can see, when I open the DIV in one hook and closing it in another one, this was working fine in WP3.5 as no wrapper was added to those hooks. Once there is a wrapper, it obviously messes up the HTML and the opening of first tab content DIV will never close, while the closing DIV has no opening counterpart. This is causing issues obviously. I would much appreciate if the wrapper in those hooks introduced in WP3.6 was somehow made optional if you are using your own, specially styled wrappers.

I understand, this is something “special” to WordPress, but I find this more screen space efficient than using classical meta boxes for additional page/post options.

(The link to the screenshot above should be still available, please let me know if it’s not.)

@moderators

As I’ve described in my duplicate deleted thread, I created it to get the answer for my issue above. I am a WordPress developer myself, I don’t need a help from WP Jobs. I posted a suggestion for WordPress 3.6, but haven’t received any answer for it…

That’s why I’ve asked what’s the best way to propose a feature fix in WP3.6? Can anyone help me with it?

Hi,

What do you mean by placement of the query?

I have the same issue but with posts:

$queryArgs = array(
 'post_status' => array( 'publish', 'private' ),
 'name'        => 'post-slug',
 'tax_query'   => array( array(
  'taxonomy' => 'post_format',
  'field'    => 'slug',
  'terms'    => 'post-format-quote',
  ) )
);
$testimonials = new WP_Query( $queryArgs );

This works pulls the post when you are logged in, but not when you’re logged out…

Thanks,

Oliver

Hi,

I can see this was not implemented in the new WP3.6 Beta 2. Could you at least give me answer why this is not being considered? Is it “bad practice”? And if so, why?

Thanks,

Oliver

[Mod note: Please don’t duplicate threads. If you need an answer urgently, try posting for support at WP Jobs]

Can I rise this as a ticket for WordPress 3.6 development? If so, can you advice how? Thanks!

Thanks for the answer. After reading the first post of this thread I’ve got the feeling that removing doesn’t work either. So I’ll try

remove_theme_support('post-formats', array(...));
remove_theme_support('structured-post-formats', array(...));

Hi, any update on this suggestion please?