Tying to update a 1733 SB site to 1873.

Front works
Login backend works
Profile works

Any other click produces an error.

Anyone with an idea?

Markus

Hello Markus,

you are not alone. - Same error when I tried to upgrade my first project. Might be a problem within german/english SF-version? ;-(((

Regards, Robert

Hello,

not only an upgrade is the problem. - I just started a new SF43-project from scratch and could establish a page. - After then I started another new SF43-project also from scratch and made it available for German and English before going to widget "pages". - At the moment when I wanted to build my first page, it suddenly crashed.

So I think, Sitefintiy Team has something to correct ....

Robert

Dear Robert

I am somehow glad I am not the only one. Did open a ticket since there is no feedback here. Will keep you posted as soon as I have an answer.

Markus

Hello,

We also have this problem and We have opened a ticket.

When we have more information, share it.

Regards

Hi all,

The problem is caused by language packs for older versions of Sitefinity used in Sitefinity 4.3. For more information, please check this article: Telerik.Web.UI.ParseException: Expression expected exception after upgrade to Sitefinity 4.3.

Kind regards,
Radoslav Georgiev
the Telerik team

Dear Radoslav

All I can say is: http://www.youtube.com/watch?v=rY0WxgSXdEE&ob=av2e

I sure hope to see the language packs updated a.s.a.p and not like in my other thread answered. We are trying to .... next week.

I really expect an 4.3 version of a multi lingual CMS to work in a multi lingual envirement.

I write you more in the ticket.

Markus


PS: Has at least the bug been fixed that the backend changes language according to front end language of the page?

Just out of couriosity

Assuming that the 4.3 language files come out some time soon. Since I can not access the backend pages to import these how would I go about it.

a) import the 4.3 language packs into the 4.2 version prior to updating

b) update 4.2 to 4.3 use the workaround to set the backen language to default EN, then import the 4.3 language files and remove the workaround?

c) is there a smarter way?

I think its very importand that the correct way to do this will be prominent placed for everyone to see. Otherwiese there will be more then one encountering this problem.

Not everybody reads my boring posts ;-)

Markus

Hello Markus Berchtold,

Please take a look at the KB article linked in my first response. It explains how to set default backend culture for the upgraded website. Setting it to English allows you to work with the upgraded website in English backend until the resources are released. Once they are released you can import them using the standard approach.

Greetings,
Radoslav Georgiev
the Telerik team

Dear Radoslav

Thanks for the answer. So everybody with backend languages other then german will need the workaround applied in order to be able to import the hopfully soon available 4.3 langauge packs.

Therefore it would be nice if somewhere it would be mentioned that you had to go through this process (kb article) if you are upgrading any SF version prior to 4.3 using other backend languages then en.

Otherwise they would run into the same trouble (spending time) as Robert and I did. Open a ticket (which will take your time) or have to go to the forum to search for an answer (take their time).

Kind of the wish of an pro active approach to this problem.

You could include a link to the KB artikel on TOP of this page http://www.sitefinity.com/devnet/forums/sitefinity-4-x/general-discussions/sitefinity-4-3-released.aspx

Markus

Is there a time frame for the 4.3 langauge packs?

I cannot update to 4.3 because of the missing language packs. I need German backend not english!

Markus

Hey Markus

Our translators are working on the translations as we speak. The German in specific is already translated, so we are verifying it as we speak, so it will be published on the marketplace ASAP.

I'll post here whenever we're ready!

Greetings,
Grisha 'Greg' Karanikolov
the Telerik team

Jeeeehaaaaa!

Great news Grisha. Finaly I can take a look at 4.3 and what's been fixed and improved.

Looking forward to the files soon. Most looked for is German, French, Italian. But German would be a good starting point. Hope you realease them seperately as soon as they are finished.

Markus

PS: I trust that you have added this to your testing scenarios (multiple backend languages) so we wont have to go through setting EN as default before updating and stuff the next time.

Hi Markus,

As mentioned in another thread, the localizations are live:

www.sitefinity.com/.../modules.aspx

Best wishes,
Grisha 'Greg' Karanikolov
the Telerik team

Dear Grisha

Great news. Now I can set the default to english, upgrade the site, import the language packs.

Thanks  a whole lot.

Markus

No luck here

Updated, uploaded site front end works.
Change the file http://www.sitefinity.com/devnet/kb/sitefinity-4-x/telerik-web-ui-parseexception-expression-expected-exception-after-upgrade-to-sitefinity-4-3.aspx as stated here.

build uploaded file and dll. Backend Dashboard is still german and if trying to access page I get an error.

a) am I doing something wrong
b) am I missing something

Hi Markus,

digging into it as we speak. We tested the language packs before uploading the newest versions to the marketplace, I am currently trying to reproduce the issue you're experiencing. I will contact you personally today to fill you in with my progress and investigate issues you're experiencing.

Best regards,

Sorry Greg, I just had to say it. "Sitefinity Sales Engineer" is the most interesting job title I have heard in a while. Wasn't sure you can engineer sales these days, but apparently you can. Sorry Greg, could not resist it. :) Andrei

Dear Grisha

Thanks. Most probably I did something wrong some where along the process. I have a tendency, as you migh now, to produce errors :-(

Markus

Hi Markus,

Do you keep a backup copy of the original ResourcesConfig.config file?

I would suggest a couple of things:

1) try importing the language pack for Sitefinity 4.3 in your Sitefinity 4.2 website prior to upgrading and upgrade.
2) try switching the default language to English, upgrade, apply German language pack for 4.3.

Let me know if these work!

Kind regards,
Grisha 'Greg' Karanikolov
the Telerik team

Andrei,

Apparently "Sales Engineer" makes more sense to people than "Solutions consultant" and better describes what I and my teammates do.
Furthermore we do have a team that trains and consults clients on their projects and the title is more applicable to them, so yes, both positions exist  .

Then again, the whole phrase "Sitefinity Sales Engineer"  might sound a bit catchy :-)

Cheers, Andrei! Have a great weekend!

All the best,
Grisha 'Greg' Karanikolov
the Telerik team

Hi all @Sitefinity,

I am looking to this described problem from far, waiting for it that it finally will run without any errors. - My opinion about this is, that there is no professional process in rolling out upgrades. As customer since 2 years with at the moment 11 different projects running with Sitefinity at each 2.000 $ and  I feel very upset about this situation.

(1) Sitefinity is offered as multilingual solution and I expect to get it in the backoffice as in the frontent.
(2) You started with eCommerce components and you did not have any idea about different tax solutions in Europe.
(3) System Updates are not in synch with Telerik ASP.NET AJAX radtools and always make problems whenever changing widgets  with user controls produced with it (Here I am moving to www.devexpress.com .... ).

I hope that this bad situation of Sitefinity would change soon ...... otherwise I am forced looking for alternative frameworks and components from other vendors. - My personal degrees of customer satisfaction are holding at MINUS ZERO.

Robert

Well thanks to personal support from Greg I was able to update my project.

The trick really was importing the 4.3 language files into 4.2 solution and then upgrade.

The confusing stuff was once it worked that no matter what backend language I did set the interface did not change (SBE). But that might be another story in another thread http://www.sitefinity.com/devnet/forums/sitefinity-4-x/bugs-issues/4-3-sbe-backend-languages.aspx  :-(

@Robert
I agree that it has been a bumpy ride and updating is always a kind of adventure. Updating this simple project took me about 5-8 hours try and error since I followed the KB article but might was trown of because the project was SBE

I agree alos that SF is not yet where it should be. We are still lagging 6 month behind in bugfixing and feature implementation.

BUT

I have looked at one competitor which offers much more for less money - and I would not want to switch because the usability of SF is simply superior to any CMS I know.

So all all can say is, hold on another 6 month (I know its a lot to be asking) but I hope that Telerik will realise that besides E-commmerce, Migration tool and new featurs like site sync -> we need all bugs fixed as well as many everyday solutions from marketplace.

e-mailing forms was finaly somewhat informaly anounced to come in spring. So try to keep a smile on your face.

Markus

Hello guys at Sitefinity,

you are really masters of desaters. - Please publish a multilingual version, that works without tricky steps forward and back as Markus Berchtold did.....

Here is my personal status after following this link:
www.sitefinity.com/.../4-3-language-packs.aspx

Have a look what happened after following ....

Serverfehler in der Anwendung /tof12.

---

Expression expected

[ParseException: Expression expected]
   Telerik.Web.UI.ExpressionParser.ParsePrimaryStart() +184
   Telerik.Web.UI.ExpressionParser.ParsePrimary() +17
   Telerik.Web.UI.ExpressionParser.ParseUnary() +115
   Telerik.Web.UI.ExpressionParser.ParseMultiplicative() +55
   Telerik.Web.UI.ExpressionParser.ParseAdditive() +60
   Telerik.Web.UI.ExpressionParser.ParseComparison() +55
   Telerik.Web.UI.ExpressionParser.ParseLogicalAnd() +55
   Telerik.Web.UI.ExpressionParser.ParseLogicalOr() +55
   Telerik.Web.UI.ExpressionParser.ParseExpression() +28
   Telerik.Web.UI.ExpressionParser.Parse(Type resultType) +31
   Telerik.Web.UI.GridDynamicQueryable.Where(IQueryable source, String predicate, Object[] values) +172
   Telerik.Web.UI.GridDataTableFromEnumerable.FillData35() +2148
   Telerik.Web.UI.GridDataTableFromEnumerable.FillData() +855
   Telerik.Web.UI.GridResolveEnumerable.EnsureInitialized() +29
   Telerik.Web.UI.GridEnumerableFromDataView..ctor(GridTableView owner, DataView dataView, Boolean autoGenerateColumns, GridColumnCollection presentColumns, String[] additionalField, Boolean retrieveAllFields, Boolean enableSplitHeaderText) +260
   Telerik.Web.UI.GridDataSourceHelper.CreateGridEnumerable(GridTableView owner, IEnumerable enumerable, Boolean caseSensitive, Boolean autoGenerateColumns, GridColumnCollection presentColumns, String[] additionalField, Boolean retrieveAllFields, Boolean enableSplitHeaderText) +132
   Telerik.Web.UI.GridTableView.get_ResolvedDataSource() +410
   Telerik.Web.UI.GridTableView.CreateChildControls(IEnumerable dataSource, Boolean useDataSource) +46
   System.Web.UI.WebControls.CompositeDataBoundControl.PerformDataBinding(IEnumerable data) +94
   System.Web.UI.WebControls.DataBoundControl.OnDataSourceViewSelectCallback(IEnumerable data) +171
   Telerik.Web.UI.GridTableView.PerformSelect() +206
   Telerik.Web.UI.GridTableView.DataBind() +432
   Telerik.Web.UI.RadGrid.AutoDataBind(GridRebindReason rebindReason) +2493
   Telerik.Web.UI.RadGrid.OnLoad(EventArgs e) +254
   System.Web.UI.Control.LoadRecursive() +95
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.AddedControl(Control control, Int32 index) +732
   Telerik.Sitefinity.Localization.Web.UI.LabelsView.CreateChildControls() +203
   System.Web.UI.Control.EnsureChildControls() +182
   System.Web.UI.Control.PreRenderRecursiveInternal() +73
   System.Web.UI.Control.PreRenderRecursiveInternal() +240
   System.Web.UI.Control.PreRenderRecursiveInternal() +240
   System.Web.UI.Control.PreRenderRecursiveInternal() +240
   System.Web.UI.Control.PreRenderRecursiveInternal() +240
   System.Web.UI.Control.PreRenderRecursiveInternal() +240
   System.Web.UI.Control.PreRenderRecursiveInternal() +240
   System.Web.UI.Control.PreRenderRecursiveInternal() +240
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3914

Dear Robert

I agree that when a language pack bracks compatibility its bad. But s... h..... as you know.

Maybe you could state again if you already did

Version Nr. 1650 for example
Version (SBE, SE)
Front-end languages
Back-end languages

Markus