Alice Brosey

Actually, calling foreach on anything not an array (FALSE is not an array) will usually throw an error. I’m not really sure what you are talking about. Of course it doesn’t iterate, but it *does* throw the error.

The second of your options, worked smoothly. The server in question was running 5.2.17.

THIS REALLY NEEDS TO BE FIXED BY THE DEVELOPERS AS I HAD TO EDIT THE PLUGIN TO MAKE IT WORK.

However, here’s what I finally found, for anyone else with a similar problem:

This file: /wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_basic_gallery/templates/thumbnails/index.php

At least in my version, the above file had hard line breaks at the end of each line, breaking many HTML tags. I went through and deleted the hard line breaks that were inside each HTML tag, and the site is now using the template properly.

Rather I suppose I figured that posting was a way to get input from the community who also develop these themes, and had no clue that posting here was going to get me slammed for having thought that a) people would read the initial question to begin with, where everything was laid out, and b) that someone might actually have some thoughts. You know, that healthy communication and discussion that leads to growth for all involved.

Clearly this is not the place for that, and heaven forbid that WordPress’s actual forums would foster discussion of… gasp… an integral part of WordPress.

esmi,

That’s why I was wondering what types of code could do it. What sorts of functions would interfere, so that I could see what might be causing it. On a general read-through of all the function files and libraries, there’s nothing obvious. Therefore, I figured asking was smart, because there might be specific things that can trigger that sort of problem, and that there would be people that might read my question who would have seen this issue before.

Actually, the theme provides no information on who made it. It’s not a premium theme, it was custom created as a one-off. I have no information on who made it, as my client doesn’t even know. It was specifically created for the single website and was not a sold theme. It may have reusable components (my theory) where the developer had built their own skeleton theme and then customized it for the client’s needs. However, there’s zero info in there except for a vague company name as designing it. (By vague, google searches on the company name, which is only initials, turn up several companies, all of which are not web development or web design.) There is no theme or developer URL to try, and I went through large portions of the theme which I thought would reveal the information to me, and didn’t.

It looks like I’m going to have to recode a new theme myself, since I don’t have a way of tracking down the problem more specifically in the theme, but it’s a complex site, and while I can do it, my client was definitely hoping to avoid the expense.

So I can’t ask for advice, as a developer, as to what could cause that sort of issue? That’s why I posted. Not for specific help or I would have provided links to code, live site, etc.

I see people frequently getting advice on how things can work and cause issues, I didn’t realize that the fact I narrowed down my problem would mean that I couldn’t get brainstorm advice from others. I’m sure this issue has happened before for other people, and all I wanted to know was what kind of code can affect the functionality of that page.

I see why I don’t usually post on the forums. If you didn’t want to help, you didn’t have to post and clutter up the thread. I didn’t come on here expecting someone to debug the theme in question. I was asking a more general question, of WHAT could affect the widgets page to eliminate the drag/drop/edit abilities without affecting the menu page. Someone might have decided to give actual input, and now it’s just a thread with 11 useless replies.

I’m sorry, clearly I shouldn’t have posted in the forum at all. I already laid out my answers to everything, above.

Specifically, I posted in the Themes and Templates forum because the Theme I am using is the definite cause. I am a quite experienced WordPress developer, and was trying to figure out what could cause this issue to happen rather than have to rewrite the whole theme, as it is a new client and the theme they already had in place.

I *know* that it is the theme causing the problem. The plugins do not cause the problem. I was trying to find out if anyone *knew* of issues which could cause that within the theme, as an idea of what sorts of code I might be looking for as the culprit.

I *did* say this in the original post, which I really wish anyone would take the time to read if they’re going to bother replying. I didn’t lay it all out to begin with for no reason, I laid it out to ask a specific question and already have that stuff answered.

I’ve verified that deactivating plugins does nothing, but switching themes to twentythirteen completely solves the issue. However, as the theme is very complex and probably would take several days to replicate in functionality as well as appearance, I am hoping someone might have advice on *where* such a problem could be occurring.

I figure that this is something other developers have run into and all I have determined is that no one on this forum reads the question in the first place.

esmi,

The problem BEGAN then. The remainder of that paragraph specified that we had since upgraded to 3.6. 3.6 just came out, it’s POSSIBLE for problems to have originated, before that.

Since it was a problem that BEGAN with a theme upgrade, I figured it would be relevant to specify the one where the problem BEGAN.

I haven’t edited my post, you should be able to see the sentence which reads “We have now updated to 3.6 in the hopes that it would simply solve the issue.”

Can someone please help me or am I just stuck getting no input at all, and getting harassed because I dared bring up an issue which started before 3.6? I haven’t ever said I was against upgrading, or that I hadn’t upgraded. In fact, I SPECIFIED that I had upgraded. I HOPED that upgrading would actually fix the issue, so I started there before even coming here.

I apologize for it being marked 3.5.2, I must have done that by mistake. I do not see how to edit that. However, the content of my question did specify, 3.6. And I did again specify 3.6.

In the meantime, does anyone have any input on what within a theme is capable of breaking the widgets page without breaking the menu editor? Or is it just “tell me to upgrade when I tell you I already have”?

Did you not read the post? I just said it broke on upgrading to the NEWEST, as in LAST WEEK, version. We have been trying to track it down since upgrading to 3.5.2 because 3.6 didn’t come out until last week.

So, what’s “old” about this?

Original post: “We have now updated to 3.6 in the hopes that it would simply solve the issue.”

Are you still looking for such a plugin? I was on here looking for some other things and my search located this query. I will be releasing a premium plugin soon which I have been working on which does this (unlimited questions + scoring to unlimited autoresponders) – let me know if you may be interested and I will link you to the plugin once it is available.

Yes and they can’t see anything wrong. I’ve put in another ticket for them to take another look, but it would be so strange to be a server error since I have hundreds of WP sites on the same server with them which are all working, beyond the one that this was cloned from.

Yes, and it’s also ridiculous because I literally moved the site – the old location still works with the exact same plugins/theme setup. The exact same. Nothing’s been upgraded since the move (on the 8th) on either location, and they’re on the same server with same FTP user.

Bump, can someone please help? I’ve used CSS to deal with the fact that they aren’t crunching, but it’s ridiculous to load a 2MB image for each thumbnail displayed. I’ve tried making everything 777 (which is stupid to require) and it doesn’t help.

They are uploading, but not crunching. It’s an installation that was working fine before moving and the old location still works fine.

THANK YOU!! I tried it out and it works perfectly! I was hoping it would be something simple to implement- would have taken me quite a while to read all the code to decide where to start editing it myself.

Thank you so much for having really, the only functioning twitter plugin I’ve found. =)