MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

Bug Report: HTML Editor NOT working in any browser, IE 8, IE 9, Mozille, Chrome Opera (Add newsletter area)  (Mono Support )

Viewed 12575 time(s), 11 post(s) 12/5/2012 7:24:57 PMby super
super

super

12/5/2012 7:24:57 PM
I am trying to add newsletter in admin area but it looks like HTML Editor NOT working in any browser, IE 8, IE 9, Mozille, Chrome Opera. I tested the bug in all browsers.

By reading other bugs of 4.7, it looks like HTML Editor is buggy in 4.7 and a lot of stuff is not working related to the editor in browsers. Also I think IE 10.

Any fix ?
This content has not been rated yet. 
6018 Reputation 709 Total posts
khorvat

khorvat

12/5/2012 8:12:19 PM
Hi, as this was already reported we have upgraded whole MonoX to support IE10 and upgraded HTML editor. You will have to use today's release or nightly build. Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
super

super

12/5/2012 8:23:19 PM
Thank Khorvat.

Another question, is it ok / safer to use nightly build for production / on live website ? since nightly builds are also like beta version so just want to make sure ?

When next version will be available i.e. monox 5.0, what difference it will make in upgrading process ? if I am using 4.7 (official release) OR nightly build ? Usually upgrade only support previous version so I just wanna make sure how it works in monox project ?
This content has not been rated yet. 
6018 Reputation 709 Total posts
khorvat

khorvat

12/7/2012 8:07:50 AM
Hi,

we don't advise anyone to use nightly builds in the production environment as sometimes major bugs can be pushed to nightly build, but in some cases upgrade to nightly build is required to fix some issue so basically if your project isn't mission critical and you are flexible / agile enough you can use nightly builds.
Another question, is it ok / safer to use nightly build for production / on live website ? since nightly builds are also like beta version so just want to make sure ?
We have announced V5.0 release date although we had to push 4.7 release date a bit further because we included some 5.0 features in 4.7 like responsive design. Upgrading to 5.0 will be a matter of doing some changes in your custom calls to the repository, bll layer and some utilities as 5.0 uses DI. So other than that I don't see any major obstacles in upgrade process.  
When next version will be available i.e. monox 5.0, what difference it will make in upgrading process ? if I am using 4.7 (official release) OR nightly build ? Usually upgrade only support previous version so I just wanna make sure how it works in monox project ?


Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
super

super

12/7/2012 9:34:56 PM
Thanks for the info

1) Version: 4.7.40.4154 (12/7/2012) - Is this nightly build safe to use for production, yes I am flexible but in future I also want the database to be upgrade smoothly with higher version (with upgrade process) so all I am concerned is, if this (or any nightly build) has some database changes (additions), it might create problem with official upgrade process when next version will be released.

any advise ?

2) In nightly builds, do you also plan to provide something like where developers / users can see the code change in official / nightly release which will help everybody to see where you have made changes and based on that we can modify our code too ?
This content has not been rated yet. 
6018 Reputation 709 Total posts
khorvat

khorvat

12/8/2012 12:42:51 PM
Hi, upgrade process is the same for official and nightly builds, so no matter if we change the database or not you can safely upgrade you app. If you use this or any other nightly build you need to be aware that you may end up with small bugs so you will need to upgrade to newer build but I suppose that in some cases this is pretty normal. My advice would be to upgade to nightly build and be flexible enough to upgrade again. As for the changes between builds we are preparing or should I say integrating patch packages, but they won't be available any time soon. My advice here would be to use source control system, perform an upgrade on your app and before you push your workie copy changes to repository check all the diffs. Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
Zoomicon

Zoomicon

12/10/2012 11:42:49 AM
For comparing between nightly build images (they have some previous versions there too) you could use WinMerge (http://www.winmerge.org) or Microsoft's WinDiff (included with Windows SDK and think Visual Studio installs it too if you select to install windows development stuff)
This content has not been rated yet. 
2793 Reputation 345 Total posts
super

super

12/10/2012 4:22:31 PM
zoomicon, thank you
This content has not been rated yet. 
6018 Reputation 709 Total posts
super

super

12/10/2012 4:22:37 PM
Khrovat,

Is this bug fixed in the official version too ? because I see the official version download says "4.7.40.4136 (12/6/2012)"

and
4.7 was released on 23 nov, 2012 so does that means, the HTML editor
with browsers bug is fixed in official release ? or should I still go
with nightly build ?
This content has not been rated yet. 
6018 Reputation 709 Total posts
khorvat

khorvat

12/10/2012 4:42:37 PM
Nightly builds always have the latest bug fixes, as you can see we considered that this issues was a major one and we updated 4.7 release version to newer version that has this bug fixed. So pick any version/stream you like and proceed, we will help you on the way.

Regards
This content has not been rated yet. 
15993 Reputation 2214 Total posts
1 2