Charlie Merland

That’s no stupid question; the simplest answer is that it makes it easier to develop and use in numerous ways. There are tools inside WordPress that make it much easier to use custom post types rather than regular posts you would have to constantly separate from movies before doing anything; using a CPT you can target actions on this post type only and leave all other post types aside, affect custom taxonomies to this CPT only, define metaboxes, etc…

The compatibility issue in another part of the problem, but I tend to see it the other way: more often than not, compatibility issues come from themes that doesn’t support custom post types or handle them poorly; but since the plugin uses regular WordPress techniques, every theme should work smoothly with it. Technically CPT are in all points similar to regular posts, except for the post_type field in the database that’s set to ‘movie’ instead of ‘post’; it’s really easy for theme developers to adapt, but obviously a lot of them just don’t think about it when working on a theme.

All considered, it is much more easier and cleaner to use a custom post type, even though compatibility with some themes can require a few tweaks 🙂

Could you paste that error message?

Thanks!

Ha, seems one link at least is missing on the official website, I’ll update it. You can still download the extensions from GitHub: Trailers and LightBox. I’m not sure at which point they’re compatible with the current version of the plugin, though, I had to set aside the dev on extensions as we’re pushing hard on version 2.0 😉 We want version 2.1 to have a really cool extension management process so we’re taking some advance to make it easier then!

It does work on my test installations; did you reload the Settings > Permalinks page to apply the change?

Sure, please try changing line 122 from:

$movies . '/([^/]+)/?$' => 'index.php?movie=$matches[1]',

To:

$movies . '/([^/]+)-your_value/?$' => 'index.php?movie=$matches[1]',
$movies . '/([^/]+)-your_value(/[0-9]+)?/?$]' => 'index.php?name=$matches[1]&page=$matches[2]',
$movies . '/([^/]+)-your_value/page/?([0-9]{1,})/?$]' => 'index.php?name=$matches[1]&paged=$matches[2]',

Let me know how this works!

Like I said earlier your best shot right now is to install a standard WordPress theme like Twenty Fourteen and activate it temporally, time enough to see if everything works with it. Then we can see what’s wrong with the plugin or the Parallax theme!

Ok, you’re actually running WordPress 4.0 and version 1.2.2 of the plugin, which is good. As for the requirements this version should work with PHP 5.3 although I’d recommend using a more recent version like PHP 5.4 or even 5.5 if possible.

Did you had any issue when importing the movie’s metadata? Are the fields filled correctly? For “Under The Skin” you should have something like this: http://pix.caercam.org/upload/original/1411024504.png

Parallax is a premium theme so I can’t provide direct support here, but you can follow up by mail to support [at] wpmovielibrary [dot] com to see if we can check this further.