Marko Heijnen

Hey Elliot,

What first forgot to say, thank you for looking into it again.

Now I know it again. It is because of acf_input::validate_page(). That will return false when it is on my admin settings page. So the metaboxes will not be called. Will play with it to add a filter in the end of the function what enable you to return true.

If I’m correct your plugin always shows the metabox right? So no checking on page template, taxonomy or any other value.

Marko

Yes that is the way how to do that in 3.0. admin_init was before and if you do it on admin_head then that should work fine too.

When looking at my reaction at the topic I’m not even sure what I meant with that:
https://www.ads-software.com/support/topic/plugin-advanced-custom-fields-the-way-the-plugin-add-meta-boxes-breaks-can-be-improvred?replies=3

I will dive into it right now.

If you read the forum here on www.ads-software.com you will see that I tried that

I decided recently that at a certain point I will remove the compatible layer or at least disable by default. Plugins should do it correctly and it isn’t up to me. This will be noted on an update this month.

And ACF I really don’t care about. I rather would suggest people to use Pods framework. That plugin already implement some changes to work nicely with my plugin.

Just played a little more with it and found some other issues.

XSLT should be loaded with set_url_scheme() so when the protocol is different the XSLT still get loaded. Setting this on $this->_url is a decision that need to be made. Maybe a filter on it would be nice so plugins can say some pages are different protocol then given.

Another issue is that XML and HTML files getting mixed up.

I was planning to release the fix last week but I’m hoping to release it some where next week.

WordPress SEO from Yoast isn’t by far the most important plugin for WP. It’s a handy plugin but it has way to much features in it.

It is the same issue. It is fixed but I need to add/change some code first.

It’s basically the fault of Yoast by doing the lazy loading of his files wrong. So I have it working now in my plugin but I can see that I will remove the code since I’m not going to fix always the mistake of other developers

At this moment it’s YouTube only. I think that will always be this way since the name of the plugin is YouTube DJ. Fix of the queue is coming but that takes time. My hope is that end of this month most of the plugin is standing how I would love to

chain was a post type and yes it was wrong. That code works perfect

I’m but first I will going to work on some core stuff till the code freeze of 3.5 (September 26).

It is definitely something to look into. Users is little bit tricky due the HTML structure.

That said there first need to be dealt with some more importent issues with post types and the UI in managing this all.

I believe this is a page you need to create yourself and add there the needed shortcode

The line on that error is wrong. I’m now trying to fix some of the issues on github.

I change the line:
$poll_answer_percentage = round((($poll_answer_votes/$poll_question_totalvoters)*100));
to
$poll_answer_percentage = round((($poll_answer_votes/$poll_question_totalvotes)*100));

There is a button in your editor on the edit page of pages. You only need to fill in the poll ID and it will generate the code. Also the code info is explained on the installation part : https://www.ads-software.com/extend/plugins/wp-polls/installation/.

looking in my current release code you shouldn’t see the notice in the develop version ?? You get the error because the tab is empty.