Adam

The problem seems to be with qtranslate X itself. In order to get it to work, deactivate qTranslate-X, then activate this plugin, then re-activate qTranslate-X again.

I don’t think it is broken. It seems the plugin uses a class on the form-tag called ‘hidden’ (as a reference to the hidden-field). Problem is that this class is generally used to actually hide a tag with CSS. You can temporarily get the form to show up by opening the developer console on your browser (F12) and disable the “display: none” on the element.

Ok, I got it to the point where it will sort off work. In inc/Google/Config.php I added:

$upload_dir = wp_upload_dir();
$up_url = $upload_dir['baseurl'];

And I changed line 89 into:

'directory' => $up_url . '/Google_Client'

This got rid of the error and when I use the default settings for a playlist, it will display that playlist.
However, when I change the default playlist into a gridview ([yt4wp-grid playlist_id="..."]), I get the text “displaying results for playlist…” but no videos.

Ok, I’ll let you know when I get it to work.

Hmm, and the provider will not lift the restrictions to the tmp dir because of abuse by hackers. I can imagine this to be a problem for more people? Wouldn’t it be an idea to let the user set the cache directory in the plugin settings? For now all I can do is change the code of the plugin and redo that every time there is an update ??

Ok, never mind. It seems it is a plugin that messes things up. my bad.

Yes, I know. But all 3 examples are not what we need, so they need to alter them afterwards and this is where it goes wrong.
It would be nice if I could add a custom self-made example to that list. (Right now this is what I did by altering your code, but that will be flushed with the next update of the plugin)

Actually, I think it should be:

add_action('init', 'types_tml_fix');
function types_tml_fix(){
    if (!is_admin()) {
    require WPCF_EMBEDDED_ABSPATH .'/admin.php';
    }
}

@paul’s solution works, except that you get a redefined error in the back-end.

Hi John,

Yes, I did manage to get it working…sort of.
I spent too much time on the problem and in the end I got something that did what it had to do, but not without bugs. For the client it was good enough and I ran out of budget, so I left it at that.
It has been a while and the project is archived, but I remember using this article as a startingpoint: https://wp.tutsplus.com/tutorials/theme-development/how-to-create-infinite-scroll-pagination/ (remember to also read the comments).
Try it, if you still cannot get it to work I could go and find the code in my project.

Ok, thanks again. However I am abandoning this line of thought since it will become near impossible to cater for every possible post/page query like this. So I am going to check the meta-key on the filters ‘the_content’ and ‘the_excerpt’ instead and use a javascript redirect or a content-change. I just hope it will not slow down the site too much.

I’ll try both of them, thanks didn’t know about the ‘loop_starts’ one. What about ‘wp’? As I understand it it will also fire before output, but I suspect it will not take custom WP_Queries into account?

Thanks, I did figure it out myself and forgot about this post. I did exactly as you say, iterating through all posts using wp_get_post_terms().
Sorry again for leaving the question open and thanks for the response.

Go to the addressbar on this page and type: https://www.ads-software.com/support/?Itemid=132 (or any other id if you want). You will be taken to the index page of this forum, not a 404. That is just the way it works.
The problem with Google indexing these pages is because somewhere on your site you must have a link that goes to Itemid=138. Find that link and remove it, and in time it will be removed from Google as well.

Perhaps WP is looking in the wrong location for its files, try adding the following 2 lines to you wp-config file:

define('WP_SITEURL', 'https://bxf.nl/');
define('WP_HOME', 'https://bxf.nl/');

I won’t say it is impossible, but it will be some work. There is a lot of content on that site which, regardless of how the data will be collated, will be tedious to work through.
First of all it will depend on how you want to setup WordPress to deal with this data. Once you have a plan for how the new site must be structured, you could probably write a script that translates the old database to the new wordpress database. But even so, you probably need a lot of handwork to check each page and item afterwards and add things like photo’s manually.