Hi folks,

I had a post over in the “How To” forum, where seth.aldridge was kind enough to teach me a few things. His help was greatly appreciated, but I still have the original problem.

The post has apparently been moved to:

http://expressionengine.com/forums/viewthread/65723/#323072

without any notice or explanation. Since I am currently using the Core version, does that mean that I’m not allowed to ask questions in the “How To” forum (or others)?

I’m almost positive that I’m going to buy EE, but I can’t do it if I can’t get that question resolved. It seems to be a pretty basic string comparison, but it just doesn’t work.

Tim

I believe all support requests regarding EE Core are almost always moved to the Core Forums, so that respondents recognize that they are discussing Core and not a full version of EE (I’ll call EE Pro).  This is really necessary for a large range of Core support issues, since a number of the solutions, fixes, etc., recommended for EE Pro, wouldn’t work in Core. Core is missing a number of features from EE Pro, which can make the support issues different.  For example, someone could have recommended a custom query solution for your issue, but that’s not really an option since you are using EE Core.  And just as a note, the EE staff move forum posts all the time. The goal is to place them where they are most appropriate to insure support.

Now regarding your original question, I’d say your original issue has morphed. Based on your back and forth with Seth, it seems that EE is parsing your {if}{/if} statements, but it is not currently producing the results that you expect. As I read through the thread, my first question was, why are you assigning a variable, for data stored in a field?

You mention that you have a field that states whether or not an ad is included. Let’s assume the field is called {display_ad}, why not just check against that field value, like:

Core users can certainly post to the How To and other community forums.  However, it appears that your thread is “I’m having a problem with X” instead of “How can I accomplish X with ExpressionEngine?”  One is a technical support issue, and appropriate for the tech support forum, in this case, the Core support forum.

without any notice or explanation

Did you not get an email notification of the move of your topic to a different forum?

allgood2: Thank you, that worked like a charm! That was the first thing that I tried, but I think that I might have been referencing the field using {has_ads} rather than just has_ads. I really, really appreciate your help.

Derek Jones: Thank you, I understand now. I did not get an email telling me that the post had been moved. I was able to locate it by clicking a link in one of the notifications that I got when Seth responded to my questions. However, the lack of a notification is probably my fault. I changed the default for notifications to not send them. I later subscribed to that thread, but I think that was after it was moved.

For anybody: Is there some reason that my assigned variable wouldn’t work for the same purpose? Here is the variable assignment at the top of the template, before the weblog:entries is called:

{assign_variable:show_div=“yes”}

Then, within the {exp:weblog:entries}{/weblog:entries} section I have this:

{if show_div==“yes”}
<div>
Hola World!
</div>
{/if}

Again, thanks to both of you. I’m so happy to get this resolved. I was really intrigued with the potential of EE and frustrated when I couldn’t get something to work that I’ve done in many other languages hundreds of times.

I’ll post one more question in this forum and then I’ll be a buyer! EE definitely fits my mindset far better than Joomla or Drupal, and I have found it to be much easier to use.

Tim

Check and make sure that the emails aren’t being sent to a junk mail folder / filter, mayest.  Moderation notifications are separate from your topic subscriptions, so one would not impact the other.

Derek, you are right. The message got filtered by Thunderbird. I marked it as “Not Junk” so hopefully that won’t happen again.