NTrost

You know, it’s possible. I seem to remember having issues that might have to do with caching on the server.

Figured I’d give an update on this issue.

After many nights of scratching my head and experimenting, I finally resolved the issue.

I’m not sure why this resolved it, but when I un-concatenated the scripts with this code in the config file

define( 'CONCATENATE_SCRIPTS', false );

which resolved it. I was then able to comment it out and the settings stayed. I’m guessing there was some issue with the order that the javascript files was being called.

Hi Ipstenu, thank you for responding.

I guess I’m not sure what you mean by “making sure my tmp isn’t full”? There are about 6 folders within that directory, they all appear to supply analytics. Most of them have minimally small sized files except for an awstats folder that has a couple of files that are a couple Mb’s each? Should I delete these?

As far as errors, the most recent errors seem to be from when I was working on a custom tool, but that was a while ago when I was trying to figure out how to customize a plugin. The plugin has nothing to do with these custom posts and I’ve since tested with it deactivated.

An update on this issue.

It appears that the image is actually uploading, but I can’t set it as the featured image. Further more, I can’t view or select any of the images in the Media Library when I go there from the post admin page. This is true for any type of post whether page, post or custom post type.

Also when I give the editor permission to add media, I can go through the media, and even though the selected images do add, they don’t confirm as being added.

This site was created in 3.5.2, and the /upload/ directory, as well as the /sites/ directory, and the directory for that individual site is set to 755.

Originally the error I got was just:

HTTP error in red

, nothing but that. Now since I’ve attempted to add all capabilities to the editor I get:

An error occurred in the upload. Please try again later. in red.

Thanks for the response,

Unfortunately I couldn’t grant anyone access of the site, but I figured it out…kind of.

I think I was calling the category type by it’s id, I think this worked fine with regular posts, it didn’t with the custom. But I found if I called the category by it’s name it works perfectly!

[sgvscroller postcount=”5″ category=”testimonials” posttype=”testimonial”]

I believe that you can either disable it within the plug-ins page of admin if it’s in there.

If not, you can disable the scripts within the functions.php page as such

remove_action( ‘wp_head’, ‘rsd_link’ );

For a CSS solution, you could probably set most of the divs as display:none, but you’d still have all of the javascript taking up load time and essentially doing nothing.

Hi

I’ve tried many variations, but this is the simplest one

[sgvscroller postcount=”5″ posttype=”testimonial”]

you listed calling the post type as “posttype”, but I also tried calling it using the more common “post_type” with no luck. I also attempted to assign a category to it, and call the category along with it, no luck.

As a quick fix for getting rid of NextGen GalleryViews added scripts, including the jquery that it pumps in. I was able to place this at the bottom of functions.php

remove_action ('wp_head','nggGalleryViewHead');

I put it into an if statement that keeps it out of all but my gallery page and admin pages. Of course I have a fairly small site, so some additional code might be preferable with larger sites.

Just figured I’d post this, as I spent a lot of time racking my brain trying to figure out how to rewrite the GalleryView script to include it into a wp_enqueue_script so I could deregister it in functions.php.

Hope this helps someone.