Havouza Posted July 5, 2022 Posted July 5, 2022 Hi! Upgrading to latesst version from our 1.1.0 does not work with the built in modules, we get a flood of errors. Now I stumbled on MigrationPro and wonder if anyone has experience with this paid module. The details text on the module page is also a little confusing about which versions it can update.
datakick Posted July 5, 2022 Posted July 5, 2022 I suggest you first investigate reasons why core updater causes "flood of errors". If there is a bug in core updater, we are happy to fix it. It is quite stable now, however. If you send me access credentials to your store (and ftp access as well), I can check the errors for you.
Havouza Posted July 5, 2022 Author Posted July 5, 2022 @datakick First you can have a look at the attached screenshot. I promise you that NO modifications has been made to any core files. I use the shop as is and is not skilled enough to change any code. And no one else has access
Havouza Posted July 5, 2022 Author Posted July 5, 2022 @datakick pressed db update OH SNAP! WE HAVE ENCOUNTERED AN ERROR Ajax request failed: error Details Response: <!DOCTYPE html> <html lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="description" content="This store is powered by thirty bees." /> <style> ::-moz-selection { background: #b3d4fc; text-shadow: none; } ::selection { background: #b3d4fc; text-shadow: none; } html { padding: 30px 10px; font-size: 16px; line-height: 1.4; color: #737373; background: #f0f0f0; -webkit-text-size-adjust: 100%; -ms-text-size-adjust: 100%; } html, input { font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; } body { max-width:600px; _width: 600px; padding: 30px 20px 50px; border: 1px solid #b3b3b3; border-radius: 4px; margin: 0 auto; box-shadow: 0 1px 10px #a7a7a7, inset 0 1px 0 #fff; background: #fcfcfc; } h1 { margin: 0 10px; font-size: 50px; text-align: center; } h1 span { color: #bbb; } h2 { color: #fad629; margin: 0 10px; font-size: 40px; text-align: center; } h2 span { color: #bbb; font-size: 60px; } h3 { margin: 1.5em 0 0.5em; } p { margin: 1em 0; } a { color: #d8b81c; } ul { padding: 0 0 0 40px; margin: 1em 0; } .container { max-width: 380px; _width: 380px; margin: 0 auto; } input::-moz-focus-inner { padding: 0; border: 0; } pre { white-space: pre-wrap; /* Since CSS 2.1 */ white-space: -moz-pre-wrap; /* Mozilla, since 1999 */ white-space: -pre-wrap; /* Opera 4-6 */ white-space: -o-pre-wrap; /* Opera 7 */ word-wrap: break-word; /* Internet Explorer 5.5+ */ width: 400px; } </style> </head> <body> <div class="container"> <h2 id="errorTitle"><span>500</span> Server Error</h2> <p id="errorMessage"> Oops, something went wrong. You can try to refresh this page </p> <p> If the problem persists please feel free to <a href="mailto:[email protected]?subject=Server%20Error">contact us</a>. Make sure to <a id="downloadError">download</a> encrypted error message and attach it to your email. That will help our engineers to solve this problem quickly. </p> <br/> </div> <script type="text/javascript"> (function() { var data = 'def50200b1667092a8cdc85a16662cafd540d7b6a29b3165462e854db1775646c5ca06cda5d9b79064a2a9ecc141e1dff5777c3a75c22bd2a2675bc97a8c4d52f2587a9583c38151207a286380913518626497eb61293095948178ea781c3c1eb8c89ca1747ab84cedd76b2779fb840595c3e5b2435d97cb69e84f3ad669635f5efb038d2d51cf2c5b44036275ad9251f5ce3e4c5a90e55ac47f859b11f667904e004ee05d0165aef8432de5f40d2ddefefcdb87231a10648c6f958fa6b4249738e39e9b4e49df16a5ed270453a5b2b41901b265079cd0da814c20787e7a97b8c0f322ae3cba123ae85d5748462d5c556cc8deb2e8787dd47e71c723c2fe7135cf59e7124cf26ac9e7ab3c0b5c3eea47aedeaae46e8d3c59fd0c85e6998ff9fcf17d9794a4991cc11145881266d29a17088389e3770fff8897f3a24ed059089dbf9fe40f6ac237d4dcb73230dd5513ce65c24cc61e633ad073d0c3ff9e40409bd095e00361ef4aef79e26401218e6caa55e4ac35d214fefee92351776c5cd70c30006286a367c8dc9322a4e172d634873b296415ad9afa4f40200a4b1e9e3c898f4cf8695e4d1dc7e15114d80357890b659a539fcb64aeaa245be91891be1cbce63f1d86971e5876baa87c1d3273b4f670546219075557fbdaaf7d48a99f3ca9871d988a6f8463047e5f3f8fc8ac3f3a9b18b7ce18976cdbf57f5edbb2b2f2d2a93940c770d90b3a54b94946a33c802aadaf855073af1b24e97b1fca9cb1c29be81242da6f90b31fd9f11d91a481f030ceda9dee29d65fb9174f9e9195420f6276416018d39d7e8fc415375b5f9e1cce7a0e04b99452e4addf9f51f131e8e1abed384f0bcbc212ba72f7c9f60ded887c54d735c8a5052539026459ed0a35630501a1ceda43bbcc96bcbd4397bcaabbc1a7d4f98489b90cb0bfeaaf8773246bfde10b8d8dae21cb423946d8e6d20031ea89521c77cffae304759a24764db28bc2b9168c8428c261fc6e3e9e7c3eda4a8554791a8a7d2c72385214490bdd674a97d8f5a268c21b72dccf8d874112c1978a965da02dc3b47851970074beab8d37fb78d4fc17c9f94b6c92c1cc040f73919707a35c5bfa37987840663aab215b92a256eb5515bb7c480f8b96400eaa4b6919f77e014eac2eda6955412de06c5832f995473cb5df4dd34b9dd8bc98e6aa4da232758727f75445a1ac0b276a1505b3ef0568c1d9e188c99ac8330c12d86b7663578cb7f96cbed5e7048297750749268585e80e3ce72061a73c6c092b56205a7e7e0debf47036c5435196c9232a855bef3c9a9dc9c0e323e9446e4adb969dc90b776ac51527bfd48b945596fc0e04b7ecf2445700cd3deaf8d55ff37736c4fea6f0753f4f4729c49932c30729881880358a2c6c913bb5e55cae46c011a2ba59fdd6f40592fa3705e31dcebadb7da02f498a5e4c91119c693ec8a930509835444e842695313b45056cf5fa069589a48361fa745fac23067a044f14133aa9cfd9d1dcbdc9d8b550428b941e808feed125f91cadcc63de27c308ad99e379622a482c02231808d173a61d8bd9fc14f2b882252fa2cd02193f8eb38853ac96930ee8c0f75ba55674019c220a921928f20354c0c9ff2203db39ab52388111c3b795dddb949ce7d9ab40028508444655f5de73f76ad55ac0ddb1e2ea81b031b9bb93d4e78259370df7f7d988a929b8f0494c2d827e6fb1ea4efddee991c3ff9315f5b6d1b92689767e0c9a9100beb9a0195c6f1f3b913aaf14c990e363a441ce2a8d18b19f7e5f71970bead7ed14c7a4610d8e6cbff5f23d083624a7bbfd76c8725014f4d2be4b42f7d42556c5daa06fbe889b2fda54a838b05874f0e165c9d45b259f80fc43f93852cb3f96bee877f7332efec2d4a06aba30888a1ac43bd466c08ddbe29ef37d47843165e5f374c81cdd6960bd87b3a03d2b76facd06aceaa04ec413ccbb2f86c08b7195e28265dce2892063f1ccbecb3f9552489af2cac0cba21de6dbeb35bc2477b3c32cbefbf37a88b9b1b71ba81aa804fb16a4c3cd8d55cb2f8cc092049ec8df1e36acb7621c0eed69dc6119683d5db04a30893edde1df2f0be4e38af024b7cfb4afc18d0bf766bed512dff6214cf8dfa01d0fed56d4011d741a4d6ff9a3f656a0c391751a182ec98c987c69afd3355ce7685c67aac73ea5f980447e4f02ecee6492b5c61f9aa5119d508179035fa0f7e0b9e287c5d8fa8f7586c2f657ae14f9bde7c707a65270ab88ea478664fcf08658aec5e64fc5f965fe10784fd9b1f4f4789ced3d9e90ffbf2a3e7b91bfd3667f68e1b4bb83ed45df3761720cd640d19830651a6941c70a2098408d46ec1524e7719993538b7db8ed6741396557ed9c13986a7a1a7c4703aefeda6c3944d1c9d4bafed0049f76c40f9e09e0da2edd021cf12f8fe2795875f81b148e3fe86c60ab55858268bf49f0040bb6d1edae4519dcefdcc2136fbec9349b362c9624ba14adfae187b0413c4b588a451439090b50134d99a941de6da3781d8e1c35f67a6b2c719790b633d948235f6d4a0c35b4cca37f1c70f0ec187a31cee1bdd5220457c7639a3de3eddd14d5dc06e832daa101025b464312f8b1cf80ef3de7a67799e4d3673964385ab0f911526eb7c989adb8c0b5ba849dcf7b98f769f0b3020bc0a69526597c85c4ecb384f4262ae6905a58f841204d5c5cb6b3cb26d7b04abfc18950abcdf7c28844745be6715b859eaccccce1548c3421b95e74e9cf72a840f024e907c2f010dc8dc8935e7a75fc1d2ce6a3e08b260629a2122a4882b4cae8bc7a0ce5f6fcc553066930c98caa6f24df5f6f1e3dcc4ce6694cceb961903d296576fe245d4fc8ae339c50e5aead7751110f0af1cfa3dac13dc2502d5287940633772365cddf75fe9eefa439a51d64e2aa84d58bf8a34cad70593a0dcd8e12b391f3bd1fcead2e221c0baee5af922c9162bba3101d6e2dc068b10a0892b933e4c1b476855cdbead108d9b582c849dd5420587441dc2e45b1bbddf4eb8e96084ad305bb1405b053ad5f0f5e0bee4e8802abfb34bd0307274e33d5cc5e60f5037c516734cb02c77b53290efbdcc0fb7090c405e08cfab99b9a2094801aed568507c6c8c02f93dfcab190781338fc6e9468da5b4847d7245b01608c67ab17fd83910f0471dad6a2d4a2f3e1f83279abec3fb1c61902ab0288169d079e794e946cfcddd4f582744f54c5c09f861f8ef5804a7312abd59dea5ce41cf4964a92eda26cf74ab1d89135fd4bf7eb4fd0c8bc99a4cb2dbae22a36199d9fb9ae2cd76c5c52c9a908cbbcadc1c9300b7bb3f7004bcc90503c93c1e472a729c5c01fee0065ecc266c38bb98a7e7d239a164f29ab2876128e214bfce95f590a9a9039b46e761ee4d6e4343772a26c38f915896851e19f3f98659d8089f3e6038d4660e3af8cfb523786c8a9176222ca3218b3252024e811777f9db2cbf77baed7aeaa9ca76ee0e7671f2b95c4731a93b8f38ca37f92050c5499fe9803943dff8e80ffd77a3f462cb0c2303c83ca91dfcfb9f7deef6663a6cbffe10c6afd26c812650f9fdd8a19aeb238710cc1ab35be60b45d20a240767c26752e8d29560d6e2e3f67cdfae44899d82784d5a98340ae1cf3e0186dde6c17072749e5b8942a412c0226bc1838eb6e761f441636a67ef1df8b40f866b5e34b28c82b73fe8897c32acdb30de059f862aa62af205e1e67f06968eedaa48dd4b36efc1b846b0e05518e182f13879fba1bd1785956592bef525c7d2052c28b47e2d0d6e608b0fea21406a5cbaba8065d3041f659d133d7809fa8f8c302c2956a5e753b2a7b79ee3a019dcba8a5c03d391ce617e32e13cc3432dbec1ee711c331947192f271a4c76a981608c12dec59eaefa4d42b6104dd29532d5cf0255f9d7f33cbdb4c266334b29a718887fdad5adf26ec530b2b25395f619a8265c6432fa3246c273ecaab668291a9606398292be32aa26911eca60219451305b1ea1862cd6b3ded5cd1324215d086084afa5cda71265b6141f18a184d4b514b4438bc0ca75647ffc174f1353558c3a178a44eb7ba0e13bd28dfb5efd727f9b9f592d962b7772b7e189b3e463253e6ca749956687a76e116ce6fa9767f8c743740c19ec7d06f01b9afdabe5954e85a08df0b4dd38af790e8d43346ee747dab6c393c97badcd794b4e560c43f28b4fb4af6269ee170f452c04dfc08b914f9604321c665e1e3363d4e550cb75c1e2cb163fed35f4a469606bc55bc337225b9fe8bca3d2f77e3fcf407e2330795e527903d12292077efcb376776f688d77652776de6a5de49e607b578b8979728d5eacd8b7ba705022c5bd787ac9f46f035694c852a20ef7a78b100054352ce1523d759c938a24cbec8a0f89afc0fe8cb4248c72285e38ab2501f36cf74517f4808a0496d5e9214f0d2cc0663056e29fdebcc44db029a957cb22c5d780dac13a8e0c7d9ff02fceca83b9ef98d9fcb28cdf76b0a0071487471a381c9e7ab19dee34f11dd2833a5f69370a530fb7000f3114ec7fc7505f92bdeee1425b8aafc55c24e1ceb9db6213fb5b879ff7e366d57d54f5c89aacc34b1b869f114c1f2c851877fc0875ea249b028d797b0bd1cd49e27f315e6cd08fcd6620a244a25f8074fae1a47d2b45ee513a00ac1216f3d0b5bf28eb3af98fb400e1962b08b1a5522c2b382b7645203adc2edbcf6d0e7c452b0f7aacaa46e810454d2f639ce26642f4cd00969377736baacd1e14898cf3e2fe8198f96d70c1cca4df94f5d89ee68c4ce54a8e86fe7440acf4bfd6e9fcdead3c4cacf239731a5c07c46e61f1d0e8df1b05dde9f0772b21197c5fc19f9924c9a7705e9bd2dc0843c69e0b392d75174490684cfaa42dac20e2b9d106314aeedf5a341372b841de8a38dba0e9b115eef58075e5d480c04b0812bce18daae0d4ef28db27068d5638722e02fbdf8221ccfce8c4e489fe0006b397642d552a08b4933f84fdd23d54d6ba9e17027491ea799e67c013356d7ff8df36c5e783769c66fc9ad13d418b7e6a4201f99ff0e3ac0c6a55da7615995296938de4f2850df67e1be90c3ec6eadbe166a43f5dade4fd6a60d32b7c8f176a9cfdcfff4b4186e59a89953e5101b7572d8a9ac5f94998914aa35f1133a28c8d8bfa6ed31de0975ebdcd3a418d7fd8cf423ea4ae29a7be6ea9c98a1a87c464722671dd493ccb265f99b868631561fa8f337587f4e76a2ed2954e6495bd041d047d6bbb743b642c95748db272b267c8e4f4fb83b91a35cfa66def26dcb9a3f5bdd3e384d24f0f9088381800cb6c127ae5bc668ba04d5c139d4ef6d1d26ec5a51bb5652fe61bd9ffc480c567f4373f02c29902b5be77f267cc8160fb573f09b58cd864d529f7f9e156331f2baec65cffbfcf5ab08efa24bd8f3fd97dc179f63609c0e8303dd1157c18ce1bbcf464845d4bd0cb10d2615aa818b5ba3be516c4f1a56e4604842cbeb6547ce38925cf6c85bbf6f42c25efbca72de6041589280c35bf357f0a2f80fac62e6c273a980e45441d60b3910c42b55ad3d2367567ddca0dfdf6f8417829a9638fc4c6a984bb3cacaf1307cfcd2a6a97476fe3111ece290c04ec4b320bf5f5bab227561428a1a2e9c828762b7d31e902b33666419f42fd8b82bc98205026cf3c684dc0ab1619bb6768cb2b1880d8eb87b78bd6431615d4d666b9a6070f37f43a5625b61e3a162d51665f1228a35abc8a21e6c2be1a9d888a830d649f17869d6ba7b839374e7804de5b9454dc9b70772fc186441988c844e78d41011f0bc004be92d900e307dae5bd165a738c158195ed4eed0c56922eda4dcb310975eb70604cc6f2ce2c847177c9b862d37c2a13b89e262d9825e1a4d246521fd237aa782d8d4006d61954bf6808d48d89d1d765b520a3a7d56f32e7292602a7735409c67f1fe4db0265d51774f912f10fd4c0954f5ce8a1f33bf1ade7f24047b561a087b6064ca596efae6bc4c623d3eb697554a6e00a187d37637cf3ef916a73829afa34cf99402e135626317b589ffcea0cf15fc77fb9a512c4026da90cb0f54c748a82c9b8ad6af3b0518a2165d614169b20ed1535ba77cf280137bc11c1f917f8a2167a237e6a04480e270a2716e7f563bb99701b6fdd21cf437a735701f8c8f623634f63ad35ccf7e024efae0ae2eda5549512c5548b163301002e6c8a653dc70bc45958d3b8273ef31899a1b358c3fbb5494975de58bdaa812a5b74a7754e72fcae361749298f26257d7959d9ebbf125583fa1de31db7148f6ca289c3c2fc9deb6603737e891719c0605fe914ba52a062d2e6a7dd14ab143e1039cf18b3aa7c97ae4611d9d9f41dc3593bb6445e9ed156259d647c09b91d93ad172ac11f2ce69f7a9970def2540521eb44dde3bc3bf41f2b673b0650714ff717598f5e8b00dc5777eb510bf473fadba432a1e5aa39aab6ea9ec93336f898329bd34f751d064efade5cde6bb1c07298a285f563e0da40f2dc5a0c85a30922e6d840a6a28bb517cc8fef49b8368e29b989a5984203d2914d0a6a58cc7aed1c17cc61cf951c3020f534941875b9783bfa2c5e25edaee76d56229d3c00a402a593086f02afa1df67ea055a6e957047d7c7f23f31012a96fe1a9089c1f341feea498622ec4fdbfc6e41727646a4e97c61ebef3e51ad7b0dce972b5bb55f2f9b92eb0fedb6c93fc969592530f26d94174d3d31a5b97feb83bdcf17257651164aa5955eff7444578dcd647a08fef567fe75e993c9964d4e32636e37c5d353cfa2d9df9c995c6737836ac7f3033051525a5c2fcadd60e36eeadb770d91c31ca07de393551a879840a5d3b15492481aae84d2b573b2c6e6a0bd119827c9c09801a08243d13bc037159b904659aa41a35c7dba1f52896f35c00f4e69c9983776af1ac8cea23b56e58e20ff2337ebbf550af7b80d6ab'; var date = new Date(); var year = date.getFullYear(); var month = date.getMonth() + 1; var day = date.getDate(); var hours = date.getHours(); var minutes = date.getMinutes(); var seconds = date.getSeconds(); var fileName = 'exception_' + year + month + day + hours + minutes + seconds + '.txt'; var element = document.getElementById('downloadError'); if(window.navigator.msSaveOrOpenBlob) { var fileData = [data]; blobObject = new Blob(fileData); element.addEventListener('click', function(){ window.navigator.msSaveOrOpenBlob(blobObject, fileName); }); } else { var url = "data:text/plain;charset=utf-8," + encodeURIComponent(data); element.setAttribute("download", fileName); element.setAttribute("href", url); } }()); </script> </body> </html>
datakick Posted July 5, 2022 Posted July 5, 2022 Your ajax request that should return json responded with html error message. This can happen when there is some fatal exception very soon in the request handler, before the controller action. I have extracted the (encoded) error message from HTML response and saved it as .txt file: exception.txt Download it, and then go to your Admin > Advanced Parameters > Logs, and use DECRYPT AN EXCEPTION MESSAGE functionality to see what went wrong.
Havouza Posted July 5, 2022 Author Posted July 5, 2022 When I try to go to logs I get a 500 server error. Have attached the file exception_202275121720.txt
Havouza Posted July 5, 2022 Author Posted July 5, 2022 It seems this all has to do with some cache problems. A couple of days ago we got an error whatever we tried to do. I sent a ticket to the forum with screenshots. I got no reaction but saw that it seemed to have to do with the snarty cache, so I tested with switching off all cache and it started to work again.
datakick Posted July 5, 2022 Posted July 5, 2022 Your current installation seems to be very broken. Try to go to Advanced Parameters > Performance, and enable Debug mode. If this is not possible (another 500 error code), then use FTP and edit file config/defines.inc.php, and change line define('_PS_MODE_DEV_', false); to define('_PS_MODE_DEV_', true); Then go to Admin > Advanced Parameters > Logs again. It should display error in plain text now.
Havouza Posted July 5, 2022 Author Posted July 5, 2022 ThirtyBeesException Unable to load template 'file:controllers/logs/employee_field.tpl' in file vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php at line 195 Source file: vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php 176: * render template 177: * 178: * @param bool $no_output_filter if true do not run output filter 179: * @param null|bool $display true: display, false: fetch null: sub-template 180: * 181: * @return string 182: * @throws \Exception 183: * @throws \SmartyException 184: */ 185: public function render($no_output_filter = true, $display = null) 186: { 187: if ($this->smarty->debugging) { 188: if (!isset($this->smarty->_debug)) { 189: $this->smarty->_debug = new Smarty_Internal_Debug(); 190: } 191: $this->smarty->_debug->start_template($this, $display); 192: } 193: // checks if template exists 194: if (!$this->source->exists) { 195: throw new SmartyException( 196: "Unable to load template '{$this->source->type}:{$this->source->name}'" . 197: ($this->_isSubTpl() ? " in '{$this->parent->template_resource}'" : '') 198: ); 199: } 200: // disable caching for evaluated code 201: if ($this->source->handler->recompiled) { 202: $this->caching = Smarty::CACHING_OFF; 203: } 204: // read from cache or render 205: if ($this->caching === Smarty::CACHING_LIFETIME_CURRENT || $this->caching === Smarty::CACHING_LIFETIME_SAVED) {
Havouza Posted July 5, 2022 Author Posted July 5, 2022 If I enable cache again ThirtyBeesException RecursiveDirectoryIterator::__construct(/home/jv80/public_html/cache/smarty/compile/3a/c7): failed to open dir: Permission denied in file vendor/smarty/smarty/libs/sysplugins/smarty_internal_method_clearcompiledtemplate.php at line 76 Source file: vendor/smarty/smarty/libs/sysplugins/smarty_internal_method_clearcompiledtemplate.php 57: $_resource_part_2 = str_replace('.php', '.cache.php', $_resource_part_1); 58: $_resource_part_2_length = strlen($_resource_part_2); 59: } 60: $_dir = $_compile_dir; 61: if ($smarty->use_sub_dirs && isset($_compile_id)) { 62: $_dir .= $_compile_id . $_dir_sep; 63: } 64: if (isset($_compile_id)) { 65: $_compile_id_part = $_compile_dir . $_compile_id . $_dir_sep; 66: $_compile_id_part_length = strlen($_compile_id_part); 67: } 68: $_count = 0; 69: try { 70: $_compileDirs = new RecursiveDirectoryIterator($_dir); 71: // NOTE: UnexpectedValueException thrown for PHP >= 5.3 72: } catch (Exception $e) { 73: return 0; 74: } 75: $_compile = new RecursiveIteratorIterator($_compileDirs, RecursiveIteratorIterator::CHILD_FIRST); 76: foreach ($_compile as $_file) { 77: if (substr(basename($_file->getPathname()), 0, 1) === '.') { 78: continue; 79: } 80: $_filepath = (string)$_file; 81: if ($_file->isDir()) { 82: if (!$_compile->isDot()) { 83: // delete folder if empty 84: @rmdir($_file->getPathname()); 85: } 86: } else {
datakick Posted July 5, 2022 Posted July 5, 2022 This is filesystem permission issues. Your php server does not have permissions to write to directories /cache/smarty/cache/ /cache/smarty/compile/ or any subdirectories / files inside these directories. Use ftp, and delete these directories completely, and then create them again. Ensure that the access permissions are valid, and that the owner is the same as the user your php server is running under.
Havouza Posted July 5, 2022 Author Posted July 5, 2022 @datakick So its the cache and compile directories I should delete and recreate?
Havouza Posted July 5, 2022 Author Posted July 5, 2022 @datakick Can you look at my first screenshot about the upgrade errors. Can I still try to upgrade it and see what happens. I will take a snapshot of the server so I can roll back if something goes wrong. I still cant get to the logs to read the textfile you sent.
the.rampage.rado Posted July 5, 2022 Posted July 5, 2022 (edited) It's very fishy if you say that you did not edit any files. Probably you had some exploit and the attacker edited some of your files. Do you use shared hosting with multiple websites in one account? EDIT: On second thought this is an expected behaviour (showing Modified next to each file) for the update module because we had it switched to different mechanism for version detection and earlier versions of TB were not detected at the exact git version but on their build version (like in your case you have 1.1 not 1f60f5da26af0092288784834e854d1a3273114e as currently they are tracked).@datakick can confirm but I think this is your 'issue' so no issue to update. Just have RELIABLE backup of db and filesystem! Edited July 5, 2022 by the.rampage.rado
Havouza Posted July 5, 2022 Author Posted July 5, 2022 @the.rampage.rado Its i virtual server and only me has any access to it. The firewall is set to only accept ftp and ssh connections from my static ip. I will take a snapshot of the server before I try to be sure. Backups can be hit and miss
the.rampage.rado Posted July 5, 2022 Posted July 5, 2022 Yes, better take a snaphot and make a manual update. 99.9% you will have no issues but it's a big update from 1.1 to edge, many things changed. Also regarding the uplodaed/edited files you may be hacked through front end, only 1 file upload is enough to do so. But probably it's the second scenario so no worries 😉
datakick Posted July 5, 2022 Posted July 5, 2022 1 hour ago, the.rampage.rado said: EDIT: On second thought this is an expected behaviour (showing Modified next to each file) for the update module because we had it switched to different mechanism for version detection and earlier versions of TB were not detected at the exact git version but on their build version (like in your case you have 1.1 not 1f60f5da26af0092288784834e854d1a3273114e as currently they are tracked).@datakick can confirm but I think this is your 'issue' so no issue to update. Just have RELIABLE backup of db and filesystem! I believe you are correct. Back in the day we didn't remember exact revision that was being used, we only remembered version. In this case, it is 1.1.0-1.1.x. Problem is that this version pointed to different revision after every commit to the bleeding edge branch. Because we now do not know exact revision, core updater compares your code base with 'current' bleeding edge for branch 1.1.x. And it will find differences, and mark them as manual changes. These warnings can be ignored now. After update this will not happen again, because core updater will remember exact revision.
the.rampage.rado Posted July 5, 2022 Posted July 5, 2022 2 hours ago, Havouza said: what kind of file should that be? As @datakick confirmed - make a backup and a snapshot and update your store and from there we will see if you have any errors present. Those warnings will be gone and TB core updater wil detect if you have any extra files in the file system.
Havouza Posted July 6, 2022 Author Posted July 6, 2022 19 hours ago, datakick said: Your ajax request that should return json responded with html error message. This can happen when there is some fatal exception very soon in the request handler, before the controller action. I have extracted the (encoded) error message from HTML response and saved it as .txt file: exception.txt 9.58 kB · 1 download Download it, and then go to your Admin > Advanced Parameters > Logs, and use DECRYPT AN EXCEPTION MESSAGE functionality to see what went wrong. @datakick Morning I tried to decrypt the message but nothing came up. I have now updated the shop to 1.3.without errors. Hope the db also got updated if necessary Thanks for all your help
the.rampage.rado Posted July 6, 2022 Posted July 6, 2022 (edited) You can safely set it to edge channel and upgrade up to the latest commit, everything is working flawlessly. Regarding db changes at top right next to Settings you see the dp upgrade option, there you will see a lot of rows, some of them saying 'dangerous'. Apply all fixes there too. Edited July 6, 2022 by the.rampage.rado
Havouza Posted July 6, 2022 Author Posted July 6, 2022 Ok I will upgrade to edge when I have fixed all the db problems. I tried to fix the charset problem using sql but it wont work so now I sit and click apply fix row by row and with 2 shops it will take some time Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now