7twenty

Update to the latest version and see if that fixes the problem. http://forum.maxthon.com/index.php?/release-notes/

When MX updates it will copy over the older flash version every time. So yes, you should keep a copy and run it after every update if you want Maxthon to always have the latest flash. It will work so long as Maxthon or Adobe don't change any filenames/paths. So no guarantee on how long it will work. Depending on where Maxthon is installed and your OS user level you may have to run as Admin as you found. I did as much testing as I could, but there still could be some things that I missed. Thanks for the feedback.

Ahhh, damn it! I even recall making that change! Forgot to add one letter!! Link in previous post updated.

Try download in another browser if MX is having issues. Although works fine here. Also check what version you already have installed: http://www.adobe.com/software/flash/about/ Been playing around with creating an auto updater seeing as fiddling around with files isn't the most user friendly thing for most people. You can try the file attached. It will detect your MX and installed flash version, update Flash if it's not the most recent, and copy over the correct files to the Maxthon folders. If you do try it, it would nice to get some feedback if it all went smoothly. Link to VirusTotal Scan: https://www.virustotal.com/en/file/15807b67a026c22bb88e93ab15d052c4cdc4d2e172013d0ee653a9bba9da2fdd/analysis/1478411287/ Gets 2 fails from some random scanners... not sure why. MX Flash Updater_0.65b.exe

Of all the users that have tested, you are the only one to have this issue. The maths and logic dictates it's a problem on your end. After going back reading through the linked thread i noticed that nowhere is it mentioned if you tested with ABP disabled (although it may have been implied with one response). Can you test with ABP off and see what happens. And nothing ever came of my last request in that thread: If this was a site error, it should happen to everyone. If this is a Maxthon issue, it should happen to everyone. If this is a userdata error, then it will only happen to the user. << this is where we're at now. If it's something else, then we need to narrow it down to what.

Long time issue for this user. No one else (IIRC) is able to replicate the same problem with bookmarks on google as he has. Zoom issue seems to be related to the extension shown.. not the built-in feature.

Maybe the UI designers can't do the backend code for the browser. So they need to keep busy with something... that said, there's plenty of UI issues to fix... Personally I remove it. It's available via shortcut, or from the reopen last tab rightclick menu. Still easily accessible (just one extra click) and i'd imagine not something that gets used all the time. More than anything probably just to unclutter the UI. Probably would have been better if they just disabled it from the default UI, rather than actually disabling it from the skin though. That's my take on why they dropped it.

Make sure "standard rendering" is enabled in settings when testing in Retro mode. BUT it works fine here in Ultra: User Agent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Maxthon/4.9.4.1100 Chrome/39.0.2146.0 Safari/537.36 OS:Win10/14393.351 (although I doubt that's the the cause)

Update from what version?

I'd be doing some major trimming of that list. 90% of those sites probably no longer exist if they're from years ago. As to why it works in previous version, I can't say.

You are running in Retro Mode. Change to Ultra and it should work.

How many favourites do you have and how big is the Favorite.dat file? If it's rather large, then that's possibly why you're running into issues with favourites. You can probably delete most (if not all) of the data in the backup folder. I always keep the latest 5 or 10 copies though. For reference i have 568 favourites and the file is 938kb. No issues on my end. You can get the total by using the update site icons feature and checking the progress meter number down the bottom. For flash to be working in Retro you need to also have the IE version of flash installed. Easiest way is to run Internet Explorer and install flash using that, as it will detect and install the right version. It should then work in Retro. Although you shouldn't have to be using Retro for youtube. Goto https://www.java.com/en/download/installed8.jsp and see if it can detect if Java is running/installed.

I think that's the issue. Up until recently they used the same userdata folder, so if anything changed due to MX5 then it may be broken in MX4. Not sure how you can fix that if it's been synced though. You already did a clean install which should have removed any local data, meaning the dodgy part is on the cloud and always gets synced. You could try the "restore defaults" option (top right) in settings. But no guarantee that will fix the issue. And you'll have to restore all your settings again. I think it's in some part that wouldn't be user accessible though. So even if you knew what part it doesn't mean it could be done. What doesn't work exactly?

With all due respect, much of what you have described seems to be user error or unfamiliarity with how things work. The text field may not always open instantly. It's either something related to your connection (eg, if it's slow/latency issues) or more than likely an issue with Maxthon and the way it deals with the script that loads it. Just happened to me, for about 1 second, then showed the box. If it doesn't show at all, then you're using a custom user agent (almost certainly the Opera or IE6-11 options). In which case using the default user agent will fix it. Because it doesn't work like that. You need to drag/drop into the box that clearly says "Drag files here to attach" with the image of a paperclip. Because again, as it clearly states "existing attachment" - meaning one you've attached previously. Click the "choose files..." link. A windows dialog should show from which you can find your file on your system.

History.dat / History_Part_[number].dat Maxthon reading the files, as no other program can without the encryption key.

Correct. But that is a backup of the corrupted data. Valid files are named History.dat for the current file, and History_Part_[number].dat for previous files. Also I believe history data files are encrypted, so there's even less chance of getting data out of it without MX being able to access it. Given that the files only contain about 1-1.5 months of history data, I can only recommend you forget about this and move on.

Delete the siteIcon.dat and siteIcon-randomnumber.dat files. Run the "update site icons" option in the favourites menu. It should restore all your icons in the favlist and elsewhere. It's a backup of the original file before it got corrupted. The data is there, but because it's corrupted new data won't get added properly and MX gives the error. Fix is as noted above.

Bahahahahahhaha Seriously this guy...

http://forum.maxthon.com/index.php?/release-notes/ I'd not update to MX5 as linked by BugMiss006, at least until it get's out of beta.

I've been using the following for quite some time: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Maxthon/4.9.3.1000 Chrome/39.0.2146.0 Safari/537.36 It's actually just the default UA with the correct OS version for my system (win10). Haven't had issues with any sites. Only one that comes to mind is occasionally a video might not play on Facebook. But reloading normally fixes that. And it is quite rare - not sure if it's UA related though. Otherwise I haven't run into any of the issues you mentioned using the above UA.

Just did a search and scrolled down about 20 times.. no crash. And that's with 10 other tabs open. Can't confirm if it's an issue with logged in accounts though.

Because they interact with the pages. If there is something wrong with, or the extension has issues or has a conflict with a site it could lead to crashes. If you don't use any, then we can discount that. Clear cache and update to the latest version

Discussed here: Thread closed - duplicate & wrong section

Update to 4.9.3.1000 Which sites are causing the crashes? Disable extensions.

What happens when you open a new tab (ctrl+t)? What happens when you go to mx://newtab ?