Thread

Copied system files, Ran update script fine.  Removed installer folder. Home page loaded great. 

Once I clear cache, I refreshed home page and get the following error:

Error Number: 1054

Unknown column 'wd.field_id_128NOT' in 'where clause'

SELECT DISTINCT(t.entry_id) FROM exp_channel_titles AS t LEFT JOIN exp_channels ON t.channel_id = exp_channels.channel_id LEFT JOIN exp_channel_data AS wd ON wd.entry_id = t.entry_id LEFT JOIN exp_members AS m ON m.member_id = t.author_id INNER JOIN exp_category_posts ON t.entry_id = exp_category_posts.entry_id INNER JOIN exp_categories ON exp_category_posts.cat_id = exp_categories.cat_id WHERE t.entry_id !='' AND t.site_id IN ('1') AND t.entry_date < 1347504480 AND (t.expiration_date = 0 OR t.expiration_date > 1347504480) AND t.channel_id = '9' AND exp_categories.cat_id = '153' AND t.status = 'open' AND t.status != 'closed' AND ( (wd.site_id=1 AND wd.field_id_128NOT LIKE "%y%") )ORDER BY t.sticky desc, t.entry_date desc, t.entry_id desc LIMIT 0, 100

Filename: modules/channel/mod.channel.php

Line Number: 2736

Looks like the NOT is being appending in the wrong spot perhaps?

Please help, I’m frustrated and would like for an update to just work for once.

I had the same issue in upgrading our site (fellowshipsj.org). It appears to be caused by a syntax issue in my code whenever I used “NOT” in search parameters for channel entries. Here’s my fix:

Change: search:body=“not pickles|shoes”
To: search:body=”=not pickles|shoes”
(See: http://ellislab.com/expressionengine/user-guide/modules/channel/channel_entries.html#search-field-name)
Hope that helps you.

Josh

Hey Jon,

Can you confirm Josh’s fix?

This is certainly not a rampant issue.

Is the error on other pages? Can we see the code in your index template?

Cheers,

Thanks for the response guys.  I should be able to try the fix in the next few days, and I’ll let you know my results.

According to the User Guide however, my current syntax should work since I’m using the documented “Contains Matching.”  Is this a correct assumption?

Allright, When I modify my code to this format: search:body=”=not pickles|shoes” The error disappears and everything works as it should.

Also, if I change not to all caps (search:body=”NOT pickles|shoes”), the page loads without an error, but no entries are displayed.

Because you should be able to use “Contains Matching” with out a = I believe there is a bug in the 2.5.3 update.

Here is the tag that breaks:

{exp:channel:entries channel='heroes' disable='categories|member_data|pagination|trackbacks' dynamic='off' status='open|Current Series' orderby='date' sort='desc' search:hero_sunday='not y' category="153"}

Hey Jon,

Sorry the delay in response, but I think the inconsistency is related to the first line in the Change Log for 2.5.3:

Added field searching across multiple sites to Channel Entries. When more than one site is specified along with a field search, all fields with the specified name used in all sites specified will be searched and entries returned. Related to bugs #17298 and #18074.

Since that code was touched, it seems we’ve introduced a new bug.

All apologies for the inconvenience.

Is there anything else I can assist you with?

Cheers,

Hi Jon,

I have the same error, and the equal sign fix works for me too.

How will this be fixed in the next release? Would we need to revert the changes?

Thanks!

Hi Creative Spirits,

If you’ve applied the fix in the bug report, no worries. That will be the code that ships in the next release of ExpressionEngine. You will simply update EE as usual and the fix will be baked right in.

Cheers,

Hi Dan,

if you refer to bug #18251 then I couldn’t find any fix mentioned there, but I assume you refer to what Josh proposed (second post in this thread).

I also noticed that if you test for an entry not being empty (=“not IS_EMPTY”) you don’t need the equal sign. This seems inconsistent. How will this be treated in the next release?

All apologies, the fix in this bug report. In there, Daniel has some code to get you fixed.

Cheers,

I’m sorry, but I have to report that I rolled back my upgrade to 2.5.3. It’s just too buggy.

After sorting out this error and other I still found plugins not working and more PHP errors.

I don’t have the time to wade through more fixes. I’m waiting for a stable release.

Could we help you with any of those issues you’re facing, Creative Spirits?

Hi Kevin,

I encountered two major hick-ups after installing 2.5.3, one of which is documented in this thread. I forgot the other one, but there is a thread in the forums that helped me solve it.

After sorting those out EE ran, but one of my plugins no longer works on certain pages (but all good on others). While I was prepared to debug (given I have written it ages ago), what stopped me was yet another “unexpected T_STRING” error on a page. That’s when I gave up.

What I as a customer would like is a separate page where EllisLabs documents such known issues for a release so users can modify their templates.

However, I’d appreciate even more a stable version where I just have to migrate and it works.

My site is a spare-time, one-man-show project (probably as many others) and at some point I had to make a call.

Thanks for your offer though.

I certainly understand. And while regressions happen in software, we obviously want to minimize those.

Regarding documenting known changes/issues, we do have version notes for any changes our engineers need to make folks aware of during an update, as well as the bug tracker which lists all known bugs. Was there some information you weren’t able to find in either of those that would help?