Thread

Hey Lori -

I believe that Robin communicated with you over email and another fix was issued for this.  Are you up and running now?

Hi Lisa,

Yes, Robin’s hotfix corrected my problem.  She instructed me that the hotfix is now part of the latest 1.7.1 download so I will use the new version for other sites that I need to update.

Thanks so much for following up and for your help in resolving my issue.

Lori

Is everyone else in the thread up and running again?

Is everyone else in the thread up and running again?

No I am not. Have the hotfix installed and on pages where I us if statements there I have this string inserted into the code “c831adif9wel5ed9e”.

Need another hotfix - the site should go live tomorrow.

Hi Werner,

I had the same problem - see post above #14 & #16.  Robin from EE fixed the issue directly on my server so I don’t know exactly what she changed.  However she said her fix was incorporated into the latest build as of Friday afternoon.  Maybe someone at EE can tell you what the exact change was so you can make it on your own since you already have 1.7.1 installed on your server.

Good luck!

Lori

Lori
I have the latest build which I downloaded today. But still have the problem.

Hmm, I don’t know then.  I was going to update another site with the latest build from today but perhaps the fix wasn’t incorporated like she said.  I’ll be on the lookout for a response from EE folks too then.

Thanks,
Lori

I was having other problems with an addon, which I didn’t know whether attributed to 1.7.1 or not, so I rolled back to 1.7.0 as part of that troubleshooting. It wasn’t 1.7.1 causing that particular error, but have stayed at 1.7.1 until I know it’s had some time out in the wild.

Thanks
Brendan

Werner,

I believe your bug is this one here which I reported this morning. I gave the bug a status of major so it will be reviewed as soon as the dev team come on-line. Related thread here

Yes John, I believe it is this one.

Thank you.

Hi, Werner. The 2.x builds were re-done this evening, but I’ll bring this up with the dev team in the morning. Sorry for not answering sooner.

This was fixed in EE 2.1.3, I just tested it.

I’m sorry…I’m confused…can you please clarify: are there any outstanding problems with the current 1.7.1 available for download or not?

I double checked this morning, there are no outstanding issues with the current 1.7.1 version available for download.

It was a build issue that didn’t creep into EE1.7.1, but did in 2.1.3 and 2.1.4 beta.

It sounded like Werner still experienced the problem on the 1.7.1 build he downloaded on April 10th.  See his post #20 above.

Thanks.
Lori

Werner? Can you double check? I can’t replicate the problem on the install I did this morning.