Doodlebee

I figured it out. Your plugin file starts with <?. When I change that to <?php it works/activates perfectly fine.

I’ve reactivated it, but I still get the same error. I haven’t been able to find what the issue is.

An update: I deactivated ALL plugins and reverted to twenty fourteen. The exact error still shows up when I activate the plugin.

Which is weird, because I looked at the code yesterday, and everything seems fine – the “}” that’s at the indicated line *should* be there (as it closes out the post function). Very strange. If I remove it, the error message shows up for line 225.

Now I’m fulfill .htaccess a way. Is it possible to add .htaccess with parameters Options All +Indexes in a directory jquery-expandable-comments/css/ ?

I’m not exactly sure what you’re asking here?

You should be able to open the .htaccess file at the root of your installation, and add that line to it. .htaccess cascades down to the folders below it. If you did that already, and it’s not working, then I’d say you need to contact your host on the issue, because I don’t think there’s anything else you can do on your end. The issue stems from how the server is set up.

There’s no index.html file in the plugin. If you added one, I guess that didn’t work (I wasn’t sure if it would). Did you add the suggested line in the .htaccess file?

Let me know if it worked ??

This is a server setting. It has to do with your host. Basically, if your host has the server to not show directory contents (when there’s no index file available) then you’ll get this error.

It’s *possible* to fix it, if your host allows you to override the setting with .htaccess. You can open up your .htaccess file and add:

Options All +Indexes

However, that will allow people to see what’s in directories if there’s no index.php/.html/.htm file present. If that’s an issue for you, another*possible* solution is to add a blank index.php file to that directory (but it’ll be overwritten in any update I make to the plugin)

I’ve checked into things, and without actually having access to a PremiumPress theme, I can’t diagnose what’s going on. I did search their forums, and it looks like custom post types are usable with PremiumPress themes, and they use the standard method (that I’m using) to create custom post types. The only conclusion I can come to is the theme you’re using (of whatever system they use for their stuff) is interfering – and it’s a bug with them. (I see they have a plugin available to their members – custom post type permalinks?)

You can open a support question with PremiumPress to see what’s going on, and if they’re willing to discuss it with me to help find a solution, you can pass along my email address: brass.blogs AT gmail.com and they can contact me directly. But from what I’ve found, it’s not an issue with my plugin – it’s an issue with their themes. (I can say with certainty that I’ve used this plugin on a myriad of different themes with no issues at all.) Without having access to whatever theme you’re using, I can’t come to any other conclusion (and I’m not dropping $599 on stuff I’ll never use, just to see what the issue could be).

Wait, are you talking about this plugin:

https://www.ads-software.com/plugins/rackspace-cloudfiles-cdn/

If so – that’s not my plugin. I have nothing to do with that. You need to go the support board for that plugin to ask your questions.

I have nothing to do with rackspace, and CDN isn’t allowed in plugins in the repository. For “optimizing a significant portion of the code”, yes, I cleaned up a lot of the old code that was int he plugins. But I’m not sure what you’re referring to, exactly. Can you clarify?

Thanks for letting me know! Not sure what I can do about that, though – but I’ll see if I can find anything about issues with recognizing post types. As far as I know, there shouldn’t be any issues – it uses standard stuff to recognize post types. But I’ll check into it.

For the record, I found a few other good tidbits of info regarding this, in case anyone else needs help:

Using the WordPress 3.5 Media Uploader within plugins

Display Media Uploader in Own Plugin on WordPress 3.5

These got me off on a pretty good start.

Thanks. Actually, I’m just curious as to what function (or set of functions, initially) that pull it in. I can’t seem to sort out how they are getting pulled in. once I know that, I can get it going – but I can’t even seem to find what function is pulling in the scripts that accomplish it. Thanks, though! I guess I’ll keep slugging through and find it on my own.

ETA: I believe I’ve found it. in case anyone else is looking for the same starting point: the function is “wp_enqueue_media“, located in includes/media.php. The script to look at is in includes/js/media-views.js. Hope that helps someone else.

Okay, I’ve just submitted an update to 1.2.2. As I mentioned in the other thread, I’m not sure what was happening – because some files were getting updated and others weren’t, for some reason. But the WP gurus helped me “flush the cache” (in layman’s terms) and now the files appear to be coming through as they should.

Thank you so much for your patience – I’m sorry it took me so long to get this sorted. Please let me know if you have any other issues!

Okay, so I just submitted an update. (I also just downloaded it to be sure, and all the files are there as they should be.) I apologize for taking so long on sorting this. I don’t know what was going on with the terminal, but the WP gurus talked with me via email and gave me a couple of tips I wasn’t aware of, and it apparently (for a layman’s way of putting it) flushed my terminal cache. I don’t know if there was some weird issue hanging out from an old commit or what, but lines were getting crossed somewhere, and it wasn’t updating all the files – just some of them. So I took the recommended advice, and it appears that 1.2.2 is now functioning and sending the correct files.

it also turns out that removing the jquery easing .js file (and switching to a cdn – something I thought would be nice) isn’t allowed. So the jquery easing file is back in there.

Thank you SO MUCH for your patience with me on this – i really appreciate it. And for helping me to get this back on track. Please let me know if you run into any other issues!