Field "DisplayName" automatic set "Support multiple language" on

Vote:
 

We have finally succeded upgrade to vercion Episerver 7.7 and Commerce 7.7. There was some struggle, but is working now.

We upgraded from 7.0, both Episerver and Commerce. Now the "DisplayName" field every time I change it to NOT support multiple languages, its changes it back in like 20 minutes (cache?).

Its run a storeprocedure "exec mdpsp_sys_MetaFieldAllowMultiLanguage @MetaFieldId=171,@MultiLanguageValue=1" when I reloade the page after 20 min, that makes the field AGAIN Multilanguage support.

Why are this happening?

Thanks

Juan

#88731
Jul 28, 2014 16:14
Vote:
 

Hi,

Do you have the stacktrace of the stored procedure call? Do you map the metafield with a strongly typed property?

.Q

#88734
Jul 28, 2014 17:45
Vote:
 

Hi Juan,

I'll note your forum thread to the support ticket you created last week.

#88739
Jul 28, 2014 19:35
Vote:
 

Quan: What o you mean about stacktrace? I dont get any error, Commerce just run the procedure. I dont man the metafield with strong type.

/Juan

#88750
Jul 29, 2014 10:37
Vote:
 

Hi,

How do you know "Commerce just run the procedure"? :) - for stacktrace I mean you might have run a profiler to find out what's running under the hood.

/Q

#88751
Jul 29, 2014 10:39
Vote:
 

Hi, 

Yes Quan, I run the SQL profiler, and I saw the procedure. I didnt know what happend...

Juan

#88753
Jul 29, 2014 10:57
Vote:
 

The only place which can possibly call that stored procedure in our code is in MultiLanguageValue property of MetaField itself. Did you make sure that there's nothing in your code call to that property?

/Q

#88755
Jul 29, 2014 11:05
Vote:
 

Hi

Yes offcource, I didnt know about that store procedure.

The first time I saw it, when I trace it with SQL profile.

Is it pocible to run it from a config files? 

#88756
Jul 29, 2014 11:11
Vote:
 

I'm going to be tricky here: When you see the stored procedure is being called, can you stop SQL Server itself? With the log turned on for both Frontend and backend sites hopefully we will get the stacktrace of calling method.

Regards.

/Q

#88757
Jul 29, 2014 11:14
Vote:
 

I understand what you mean...

The thing is, before that SP run (mdpsp_sys_MetaFieldAllowMultiLanguage), runs other SP to authenticate the logged user, and I will not see the tracktrace that the SP it will throw the other SP error.

Or what do you think?

#88759
Jul 29, 2014 11:46
Vote:
 

Yeah. We can simply drop that stored procedure, then we will got the exception with the stacktrace of calling method!

Can you do it then post the stacktrace here (or send it to me?)

Regards.

/Q

#88774
Jul 30, 2014 12:14
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.