Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Raymond

Members
  • Content Count

    21
  • Joined

  • Last visited

  • Days Won

    1

Raymond last won the day on September 7

Raymond had the most liked content!

Community Reputation

4 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello Everyone I tried to upload products from Store Manager 2.57.0 build 2233 to thirtybess 1.1.0 and everything seems fine. The test included upload of catalogue from CSV containing products, then I tested creation of products and upload, upload images, specific prices, attributes, so far for that I noticed no problems, except having to clear the cache sometimes when I uploaded new specific prices. I do not know if the cache cleared was the solution, however it happened to upload specific prices, see it in the back office product and not in the front office, I deleted the specific price, created it again in the back office and then worked, out, I also cleared the cache and after that all other specific prices in other products worked normal, the created other specific prices in store manager and uploaded it and they all worked fine without having to repeat that test procedure of creating it form back office and or clearing cache... do not know how to explain this behaviour, however it works now after that first "thing". Hope this help. Again, I suggest to everyone to ask EmagicOne to support ThirtyBees. Bye R.
  2. Hi Signut Yes, I renewed anyway the Store manager update license and I regularly update it, I am also pretty concerned about Store manager loosing ability to manage TB, it would a real bad thing. Right that the reason for which I advice everyone to write to Emagicone about how good is the idea to also support TB too, in fact for them should not be hard at all as it is already fully compatible with PS 1.6 and starting from there should not be a problem to collaborate with Thirtybees too so keep their old customers (as an example you did not renew the update period, if they realize that those who will do that are many they have to change their mind) but also get new clients. Also is good to spread around good words for TB, the more are the users the more are the chances to get on well and fine. @ Betty Nutz > I am working on my CSVs and will test soon, I will report what happens Thank you Regards
  3. Hi I am going to use Store manager 2.57.0 with TB 1.1.0, I hope that will work fine I will let you know how the test goes So far as Signut wrote here above that with a previous Store manager version can work on TB 1.1 I imagine should be fine, at least partially. In fact by the way I am worried about the changes done on the database on the TB 1.1 version, surely are not taken in account in Store manager at this point and I have no idea if this is going to cause troubles. My questions is about those extra tables introduced in the DB, can anyone expert predict if Store manager is going to do troubles in this respect? I guess that at Emagicone they said that are not going to support Thirtybees as at that time they could not foresee how much people is going to use it. However of course they might very well change their mind, they do support several e-commerce platforms, they will support also Thirtybees if becomes popular enough, there is no reason why they should not do it in that case. Also would help much to let know Emagicone people that one switched to Thirtybees and ask to support it. I am going to write them about, furthermore I suggest to everyone to do the same, and also to spread a good word around for TB so to help increase the success of this project. Anyone who use TB and have already Prestashop store manager of course have full interest in achieving Emagicone to support it, but I would say also anyone else might like to support the TB success, even if is not going to use such a tool, in fact would be just a good thing to have TB recognized as interesting solution by more well known companies. As usual in this cases could also be good to join the forces and create a collective petition too to Emagicone. Who is going to support this action? Thank you Best regards to everyone R.
  4. Hello Yaniv I also used this module in a old 1.5 prestahop installation, it worked very well as it eliminates that bulky thing the prestashop people thought (practically an automatic obstructor machine as it was originally conceived). I confirm that the AWP module eliminated all the attributes trouble in my old PS shop. I am very encouraged by your comment, is a pretty good info the fact that you already successfully tested it on TB. So far, coincidentally with your reply that I read now, I installed and tested the 1.8 version right today on TB 1.1 using the ST Transformer theme, but I see troubles in the FO To start with to fix this I think I really need to get the latest version 1.8.0.3 (it is the only declared by Presto Changeo to work with TB), secondly I found a bit hard recognize how to exactly modify all the files in the transformer theme. One thing that is a bit complicate when installing this module is to avoid errors adding all those lines in all those files, especially if the theme used if quite different from the default one... I am waiting now to receive the updated version, I will test it as soon as possible, I am pretty confident that should work well, I just hope to succeed to properly modify the transformer theme files. Thank you. Best regards
  5. Hello Petr And Colorful Ant I guess that when the combinations are too much the same happens maybe for the same reason Petr explained for the features. So, for what is concerning the amount of combinations of a product, as too many are going to affect also the speed at which the Front office product page is shown to the potential customer, maybe the only solution is to keep the combinations at minimum necessary. Eventually a workaround is to create another similar product with the other combinations left, maybe adding a link in both the products page to see in each the other similar product with extra combinations (hoping that the potential customer see that link, often clients are very fast in dismissing pages). As far as I know there might be a module that solve the product combination generation trouble, but I am not sure that the FO slow page problem is solved. For the features I do not recall to have seen slow pages in the Front office, the trouble is confined in the BO as far as I know (to be checked tough). Also in the layered navigation system there should be no big problem in th FO, when I had it up with all those features everything seemed to work fine, maybe a bit slow, but, for who understand how much useful is that filter should not be a problem to wait some more seconds to have it ready (that was in prestashop 1.6, but I guess will be the same in TB1.1 if not better) That overall to me means that at the moment, due to the old prestashop architecture in this respect, a TB shop might not contain a great amount of features and/or products with a lot of combinations. Until one build a shop for own use knowing these limits helps to keep it reasonable, eventually the BO trouble is bypassed using some tools alike phpmyadmin, store manager or the like. The situation is different if one is preparing the shop for a client, in that case one have to warn that having a lot of features there might be troubles in the BO and troubles in the FO if products must have a lot of combinations, that is a different and more complicated scenario. It is always hard to explain to a potential client why a solution is good even if it contains special limits, besides that a client might be concerned about the possibility to be able to use the shop in case the need of using lots of features and combinations might arise in a future, (or plain simply need that great amount of features and combinations since start, case for which would be hard to opt for TB). Than you Best regards
  6. Hello Petr Tired of prestashop continuous fails, very annoyed by the fact that a good amount of addons I bought for prestashop did not work out of the box, having lost a great amount of time, patience, money, trust... I ran into a real disillusion and stopped dreaming after prestashop. Prestashop is for me now only a big loss of time. I decided to leave it after I saw how bad is 1.7 version, how they could never ever end any project for good, how much I did not like at all their marketplace, how I do not like also their forum.... and so on. However I recognized the great potential of prestashop up to version 1.6. When I came to know about Thirty Bees I got very interested as in the meantime looking for alternatives sincerely I could not find something that overall is as much interesting. Considering the past experience and knowing how painful can be to have a decent shop this time I elected Thirty Bees and to deploy it I created a couple of TB clones to test in steps, one branch to do new things and a "step behind branch" to check and eventually revert, so I have a certain freedom into going forth and back while building up the platform I need. I can do that too and report, but I need some time, by the way, if Tb was not fixed to avoid that issue, very likely is present in TB 1.0.8 as well. However, if I discover that with TB 1.0.8 I can create all features that I want while in TB 1.1 the limits is a few dozens of features, in general that would be a very strong limitation either ways. So this test can be done for curiosity I guess, but discovering that version 1.0.8 is not affected won't solve anything for the users as would make little sense to get stuck into the 1.0.8 version. Tjis issue is nothing that causes a "no no" answer to the question "would you use thirty bees?", but, still, that kind of limit leads one to say for good in a bit emphatic way "for a big complex shop there might be troubles in certain circumstances". I think that statement in various extents is true with any platform, but surely it can have a different weight, for instance a big one if the possible circumstances are many and maybe due to some apparently minor things, alike a major page in BO using a script that gets clogged, busy and not responding. Products can be handled via database eventually using some very efficient tools, but, the point is that in the BO for obvious reasons everything must work well. Even if the problem can be circumvented and avoided with external/third party means, in general, having such a limit in the BO is not good at all for several reasons, licenses costs, clients needs, clients preferences, employees not having access to special tools but maybe needing to apply few changes on the fly and so on, there are many possible examples... One example is my own experience with this issue, I resume here what happened and what will likely happen: I hit this trouble not knowing why except remembering that happened already in prestashop sometimes, consequently did a search to guess what can be, wrote a post here and continued to investigate, got an idea about it and finally saw that is an old prestashop issue due to excessive product features, but also and/or maybe categories and/or attributes, so I reverted, clarified that in my case is the amount of product features, had to reason on it, wrote updates to the post here, now I am deciding to add again little groups of products features in steps to try to guess then which is the limit to not see issue again, after all that, if everything goes fine, knowing the eventual limit I will have to decide how the shop must be pruned to not have the problem.... I do not like the idea to have to guess a limit in order to prune the shop... is not good. However this is just what I will do as I am unable to solve the problem except try to see if anything good happen with some changes that are suggested or that I can random find on other posts with more extensive searches on internet That is surely not the convenient and desired workflow I would like to have, but very probably nobody would like to have such an adventure... This trouble as far as I understood is inherited from prestashop, in that post on github I linked ( https://github.com/PrestaShop/PrestaShop/issues/9809 ) presta people admit it and in many occasions apologize to persons writing heavy complaints about this issue, mainly spotting out how it is a strong limit impeding having things right in a growing shop or anyway a big shop (as I read because they feel alike being ignored, a feeling that in general is not hard to recognize in the prestashop thing) While developing any project being continuously stopped by some little stones in the shoe is really not nice, especially if one find no easy way to remove it... In general one want to just go on and publish at least having the basic things well done right, the rest can be done later on. As anyone can imagine even working onto a perfect bug free platform there is a lot of work to be done to have a working shop. My greatest wish giving trust to the TB project is to become able to concentrate much on that commercial part and not have all kind of technical problems meanwhile I do work on selling products. That in the latter sentence might be a reasonable goal also for developers of an any business software platform as when micro and small business find a lot of difficulties to start or to grow a HUGE amount of potential future customers are cut out of the game while the few notorious big and monster giant companies gather everything at faster speed. This is not a critic, I just wanted to describe what/how it all happens and why things alike these can be very frustrating. That said while I try to fix my thing here, within my limits, I am very keen on helping, ask me anything and I'll contribute as a final user tester as much as I can. Thank you for the help Best regards Ray
  7. Hi Petr I remember to have read about the smarty engine version change, due to my ignorance I did not get immediately that this is the culprit for those minor changes now necessary in the third parties themes, or simply I forgot about that right after reading it, but I kept as true in my mind that changes were necessary. Thanks to your precise explanation written in perfect divulgation language style I now I fully understood the whole case. I am very happy of the work done by the Thirty Bees team, according to me as a final user is very good and reasonably I am pretty keen on accepting changes when really needed, we must be very reasonable in this respect. Thank you. Best regards Ray
  8. yes, I got it, I will try that, thank you However, as far as I understand, maybe that modification is going to avoid the long response and the error message, I do not know if it is the only trouble... however, I will test it and report. Variants... you mean product attributes? Yes I have many and maybe will add more in future, is very useful function to avoid a lot of product pages and/or avoid confusion to clients and search engines. However at this stage I am testing with the sample products present at installation time, so a few combinations are in use.
  9. Alright, yes, I got it, it should be that way, logically retro compatibility should be maintained. I do not know if this is a strict guideline in the TB roadmap and constitution, as I hope it is, in fact I feared that event of retro compatibility breach and it happened, that was not good to be seen. However, I can understand that some changes might be unavoidable at times and some exception might be justified if the advantages obtained are really important and great. Overall I truly hope that is possible to strongly enhance the system without throwing in the trash the whole addons/themes catalogue, would make no sense at all and would reproduce the Prestahop 1.7 "disaster". Now, as not expert, I am not capable to discern if in this case this incompatibility is due to just something missing/erroneous in TB 1.1 or because any major change imposed to break something, from what you wrote I understand now that this is very simply some error or missing thing in the TB 1.1. All what I understand of this is a derivation of what I can read here in this forum and other sources, + my non expert reasoning, reading that "a new version of panda, compatible with TB, will be released... " lead me to think that in TB 1.1 there are some unavoidable changes, if that is not the case, well, I stress on the concept of retro compatibility. I am here because I found the prestashop policy a total failure (almost an insult to everyone, developers and end users). I do not like that kind of scissor used in such not careful, senseless and lousy way in a development line (especially if the result is a tasteless buggy sort of soup alike just as prestashop 1.7 looked to be to me...) Either ways, I hope that in future this is not going to be a problem, retro compatibility is too important to avoid serious troubles.
  10. Hello Occam The action and consequent error that comes out exactly is this one: 1) I click on Catalog menu and open the Product list tab, there I click on a listed product edit button to edit it 2) the product edit page is loaded, but is soon halted, I cannot navigate in it, after some more seconds (10 or alike) the progress spinner goes on again and is possible to scroll the page, this already take alike 20 seconds or more, however the page at this stage, still, is unusable. 3) After some other 10 to 20 seconds a popup error message appear telling exactly the message I posted: jquery-1.11.0.min.js:3 script busy or not responding This popup error message allow to "Stop the script" or "Continue", if one stop the script cannot use the page, of course it becomes useless, if one click "Continue" the script is further processed, so after more dozens of second finally the page becomes fully available. If the debugger (in firefox) is opened, that same message allow a third option, "Debug the script", if that one is chosen a lot of info comes out, however I am unable to interpreter it correctly. By the way I have seen that there are quite some warnings about CSS problems, a couple of scripts in which the character encoding is not declared so if used out the frame in which are inserted might show odd stuff, and more stuff, I can post it all if useful... However, as I am not expert, I am not sure to have searched well in the debugger in order to get the most relevant info for this specific problem, I have the feeling that I saw quite many errors and warnings that might be unrelated. If you can suggest me what to exactly do with the debugger I can reproduce again the problem and post a full report. Thank you
  11. I am sure that Transformer and Panda can become fully compatible with TB 1.1, however as we saw a few fixes are still necessary, would be very nice of Sunnytoo to fix it all and include it in their releases for both themes (I guess that they are going to do it hopefully). I am testing ST Transformer under PHP 7.1, TB 1.1, it works fine apparently, but still I did not test many features, alike layered search, combinations, specific price reductions, bundles and so on. In fact after adding a lot of features , lots of attributes, some suppliers and manufacturers, wanting to begin to test related products, combinations, specific prices, and layered navigation I got stuck because of a Jquery problem, I opened a post for that: I am going to revert step by step hoping to find what where the changes that lead to it. Btw, this halted my tests, I am not keen on waiting minutes each time I attempt to edit a product and in general to ignore this issue, need to have it fixed and understand what causes it. Because of that I still have to see if everything else works fine with Transformer (and would really like to, I am a bit in a hurry to publish the new website).
  12. Hello In BO page to edit/create a product I get this error jquery-1.11.0.min.js:3 script busy or not responding If I do click continue after a while the page work, in other cases clicking continue result in a halt of the browser and eventually a crash. Clicking stop the script results in not being able to save the changes. What should I check to debug this? Thank you. Regards Ray UPDATE I begun to see this error after I added a few things: suppliers, manufacturers, attributes, features and relative default values, etcetera... I reverted step by step and discovered that this issue is caused by the features. The addition was done via phpmyadmin directly in the database, everything else seemed to work fine, only this jquery issue was triggered, now thinking about this (as noob) I might thing of 3 possible scenarios: 1) in the tables I used (taken from previous prestashop installation I am using) there might be errors and incompatibilities with TB, however I took care to compare the feature related tables structure one by one, all seems fine for each. For what is concerning the values in the tables I took care to check that are consistent, so far I think that are fine, I do not know what eventual special thing need to be checked to avoid inconsistencies or conflicts 2) the character encoding might be wrong for these tables, in fact in the values assigned to features there might be some rarely used character causing troubles, alike °, the diameter symbol, and few others... I do not know if the use of such characters can cause such an issue as a jquery script busy or not responding 3) the amount of features, default values and languages is quite big, over 180 features, about 4800 default values and because there are 10 languages in use over 48000 record in the table feature_value_lang, I do not know if using many features and default features can cause such an issue Can anyone tell if the size of the tables can cause this problem? (I can start recreating everything from the BO and check now and then while progressing if the page to edit a product start to cause this trouble again, but is a very long work I would like to avoid). IF that of the size of the tables is a known problem I would avoid bothering doing all those tests and search for the proper solution to that... What about the other two possibilities I am imagining? (I am not expert, I am working according to my understanding and imagination, sorry...) What do you suggest to investigate first? Any other thing to check in order to solve this? FURTHER UPDATE I found this page on github: https://github.com/PrestaShop/PrestaShop/issues/9809 Seems that there are several troubles with amount of categories and product features in prestashop 1.6 and 1.7, as TB is containing large part of PS 1.6 I guess this trouble is inherited. It is a quite odd trouble, very annoying and a big limitation. Is TB also still affected? What do you suggest to circumvent this? Anything else is known in relation to this issues? Thank you Best regards Ray
  13. Hello Brent Thank you for the info. No, transformer is not compatible with TB. Yes Panda should be, but not sure about TB1.1 Thanks Ray
  14. Hello I upgraded from TB 1.08 to 1.1 All seemed fine, then I found out to have to see the order status page in order to have the database fixed creating two columns that core updater still does not do However further testing i discovered that in the checkout process having the native OPC activated I get a 500 internal error page. In the error message there is a link to download an encrypted error log, how can I decrypt it to read the content? So I switched to the 5 steps checkout, this work, but the custom payments I created are shown four times each. I do use transformer theme. What should I look at to give you more info? What can I do to fix this? Thank you Kind regards About using the OPC I reached to get this error message ThirtyBeesException Cannot use object of type Carrier as array when rendering smarty template themes/transformer/order-opc.tpl Source file: themes/transformer/order-opc.tpl 1:{* 2:* 2007-2014 PrestaShop 3:* 4:* NOTICE OF LICENSE 5:* 6:* This source file is subject to the Academic Free License (AFL 3.0) 7:* that is bundled with this package in the file LICENSE.txt. 8:* It is also available through the world-wide-web at this URL: 9:* http://opensource.org/licenses/afl-3.0.php 10:* If you did not receive a copy of the license and are unable to 11:* obtain it through the world-wide-web, please send an email 12:* to license@prestashop.com so we can send you a copy immediately. 13:* 14:* DISCLAIMER 15:* 16:* Do not edit or add to this file if you wish to upgrade PrestaShop to newer 17:* versions in the future. If you wish to customize PrestaShop for your 18:* needs please refer to http://www.prestashop.com for more information. 19:* 20:* @author PrestaShop SA <contact@prestashop.com> 21:* @copyright 2007-2014 PrestaShop SA 22:* @license http://opensource.org/licenses/afl-3.0.php Academic Free License (AFL 3.0) 23:* International Registered Trademark & Property of PrestaShop SA 24:*} 25: 26:{if $opc} 27: {assign var="back_order_page" value="order-opc.php"} 28: {else} 29: {assign var="back_order_page" value="order.php"} 30:{/if} 31: 32:{if $PS_CATALOG_MODE} 33: {capture name=path}{l s='Your shopping cart'}{/capture} 34: <h2 id="cart_title">{l s='Your shopping cart'}</h2> 35: <p class="alert alert-warning">{l s='Your new order was not accepted.'}</p> 36:{else} 37: {if $productNumber} 38: <!-- Shopping Cart --> 39: {include file="$tpl_dir./shopping-cart.tpl"} 40: <!-- End Shopping Cart --> 41: {if $is_logged AND !$is_guest} 42: {include file="$tpl_dir./order-address.tpl"} 43: {else} 44: <!-- Create account / Guest account / Login block --> 45: {include file="$tpl_dir./order-opc-new-account.tpl"} 46: <!-- END Create account / Guest account / Login block --> 47: {/if} 48: <!-- Carrier --> 49: {include file="$tpl_dir./order-carrier.tpl"} 50: <!-- END Carrier --> 51: 52: <!-- Payment --> 53: {include file="$tpl_dir./order-payment.tpl"} 54: <!-- END Payment --> 55: {else} 56: {capture name=path}{l s='Your shopping cart'}{/capture} 57: <h2 class="page-heading">{l s='Your shopping cart'}</h2> 58: {include file="$tpl_dir./errors.tpl"} 59: <p class="alert alert-warning">{l s='Your shopping cart is empty.'}</p> 60: {/if} 61:{strip} 62:{addJsDef imgDir=$img_dir} 63:{addJsDef authenticationUrl=$link->getPageLink("authentication", true)|escape:'quotes':'UTF-8'} 64:{addJsDef orderOpcUrl=$link->getPageLink("order-opc", true)|escape:'quotes':'UTF-8'} 65:{addJsDef historyUrl=$link->getPageLink("history", true)|escape:'quotes':'UTF-8'} 66:{addJsDef guestTrackingUrl=$link->getPageLink("guest-tracking", true)|escape:'quotes':'UTF-8'} 67:{addJsDef addressUrl=$link->getPageLink("address", true, NULL, "back={$back_order_page}")|escape:'quotes':'UTF-8'} 68:{addJsDef orderProcess='order-opc'} 69:{addJsDef guestCheckoutEnabled=$PS_GUEST_CHECKOUT_ENABLED|intval} 70:{addJsDef displayPrice=$priceDisplay} 71:{addJsDef taxEnabled=$use_taxes} 72:{addJsDef conditionEnabled=$conditions|intval} 73:{addJsDef vat_management=$vat_management|intval} 74:{addJsDef errorCarrier=$errorCarrier|@addcslashes:'\''} 75:{addJsDef errorTOS=$errorTOS|@addcslashes:'\''} 76:{addJsDef checkedCarrier=$checked|intval} 77:{addJsDef addresses=array()} 78:{addJsDef isVirtualCart=$isVirtualCart|intval} 79:{addJsDef isPaymentStep=$isPaymentStep|intval} 80:{addJsDefL name=txtWithTax}{l s='(tax incl.)' js=1}{/addJsDefL} 81:{addJsDefL name=txtWithoutTax}{l s='(tax excl.)' js=1}{/addJsDefL} 82:{addJsDefL name=txtHasBeenSelected}{l s='has been selected' js=1}{/addJsDefL} 83:{addJsDefL name=txtNoCarrierIsSelected}{l s='No carrier has been selected' js=1}{/addJsDefL} 84:{addJsDefL name=txtNoCarrierIsNeeded}{l s='No carrier is needed for this order' js=1}{/addJsDefL} 85:{addJsDefL name=txtConditionsIsNotNeeded}{l s='You do not need to accept the Terms of Service for this order.' js=1}{/addJsDefL} 86:{addJsDefL name=txtTOSIsAccepted}{l s='The service terms have been accepted' js=1}{/addJsDefL} 87:{addJsDefL name=txtTOSIsNotAccepted}{l s='The service terms have not been accepted' js=1}{/addJsDefL} 88:{addJsDefL name=txtThereis}{l s='There is' js=1}{/addJsDefL} 89:{addJsDefL name=txtErrors}{l s='Error(s)' js=1}{/addJsDefL} 90:{addJsDefL name=txtDeliveryAddress}{l s='Delivery address' js=1}{/addJsDefL} 91:{addJsDefL name=txtInvoiceAddress}{l s='Invoice address' js=1}{/addJsDefL} 92:{addJsDefL name=txtModifyMyAddress}{l s='Modify my address' js=1}{/addJsDefL} 93:{addJsDefL name=txtInstantCheckout}{l s='Instant checkout' js=1}{/addJsDefL} 94:{addJsDefL name=txtSelectAnAddressFirst}{l s='Please start by selecting an address.' js=1}{/addJsDefL} 95:{addJsDefL name=txtFree}{l s='Free' js=1}{/addJsDefL} 96: 97:{capture}{if $back}&mod={$back|urlencode}{/if}{/capture} 98:{capture name=addressUrl}{$link->getPageLink('address', true, NULL, 'back='|cat:$back_order_page|cat:'?step=1'|cat:$smarty.capture.default)|escape:'quotes':'UTF-8'}{/capture} 99:{addJsDef addressUrl=$smarty.capture.addressUrl} 100:{capture}{'&multi-shipping=1'|urlencode}{/capture} 101:{addJsDef addressMultishippingUrl=$smarty.capture.addressUrl|cat:$smarty.capture.default} 102:{capture name=addressUrlAdd}{$smarty.capture.addressUrl|cat:'&id_address='}{/capture} 103:{addJsDef addressUrlAdd=$smarty.capture.addressUrlAdd} 104:{addJsDef opc=$opc|boolval} 105:{capture}<h3 class="page-subheading">{l s='Your billing address' js=1}</h3>{/capture} 106:{addJsDefL name=titleInvoice}{$smarty.capture.default|@addcslashes:'\''}{/addJsDefL} 107:{capture}<h3 class="page-subheading">{l s='Your delivery address' js=1}</h3>{/capture} 108:{addJsDefL name=titleDelivery}{$smarty.capture.default|@addcslashes:'\''}{/addJsDefL} 109:{capture}<a class="btn btn-default" href="{$smarty.capture.addressUrlAdd}" title="{l s='Update' js=1}">{l s='Update' js=1}</a>{/capture} 110:{addJsDefL name=liUpdate}{$smarty.capture.default|@addcslashes:'\''}{/addJsDefL} 111:{/strip} 112:{/if} Stack trace 1. vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php:128 source content_5d476ec0a291a0_45265484(arguments) 2. vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php:172 source Smarty_Template_Resource_Base->getRenderedTemplateCode(arguments) 3. vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php:206 source Smarty_Template_Compiled->render(arguments) 4. vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php:372 source Smarty_Internal_Template->render() 5. Smarty_Internal_Template->_subTemplateRender(arguments) #1 ".../themes/transformer/./order-carrier.tpl" #2 null #3 null #4 0 #5 31536000 #6 array(0) [] #7 0 #8 true 6. vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php:128 source content_5d476ec059c640_53267765(arguments) 7. vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php:172 source Smarty_Template_Resource_Base->getRenderedTemplateCode(arguments) 8. vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php:206 source Smarty_Template_Compiled->render(arguments) 9. vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php:216 source Smarty_Internal_Template->render(arguments) 10. vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php:107 source Smarty_Internal_TemplateBase->_execute(arguments) 11. classes/SmartyCustom.php:180 source Smarty_Internal_TemplateBase->fetch(arguments) 12. classes/controller/FrontController.php:984 source SmartyCustomCore->fetch(arguments) 965: $this->js_files = Media::cccJs($this->js_files); 966: } 967: } 968: 969: $this->context->smarty->assign( 970: [ 971: 'css_files' => $this->css_files, 972: 'js_files' => ($this->getLayout() && (bool) Configuration::get('PS_JS_DEFER')) ? [] : $this->js_files, 973: 'js_defer' => (bool) Configuration::get('PS_JS_DEFER'), 974: 'errors' => $this->errors, 975: 'display_header' => $this->display_header, 976: 'display_footer' => $this->display_footer, 977: 'img_formats' => ['webp' => 'image/webp', 'jpg' => 'image/jpeg'] 978: ] 979: ); 980: 981: $layout = $this->getLayout(); 982: if ($layout) { 983: if ($this->template) { 984: $template = $this->context->smarty->fetch($this->template); 985: } else { 986: // For retrocompatibility with 1.4 controller 987: 988: ob_start(); 989: $this->displayContent(); 990: $template = ob_get_contents(); 991: ob_clean(); 992: } 993: $this->context->smarty->assign('template', $template); 994: $this->smartyOutputContent($layout); #1 ".../themes/transformer/order-opc.tpl" 13. classes/controller/Controller.php:226 source FrontControllerCore->display() 14. classes/controller/FrontController.php:253 source ControllerCore->run() 15. classes/Dispatcher.php:837 source FrontControllerCore->run() 16. ./index.php:33 source DispatcherCore->dispatch()
  15. Hi Well ^^, then I got a version 1.0.8 where that extra dialogue to decide which modules enable or disable is already removed. Yes, in fact I was used to install the theme and find it ready as the developer intended to present it, then of course one could always change a few thing or many things. In this case I got this theme with over 30 modules or alike and was a sort of pain to disable all duplicate function modules from TB and enable all the modules of the developer, that apge was useful as one could decide whatever, leave everything as the developer suggests, keeps everything as it is of fast decide what to do on the spot, eg. disable some less or more and viceversa enable less or more of the new modules according to needs or preferences.... I missed that page 🙂 By the way, so far is good to know that is not just a bug but effectively was removed, while I hope you bring it back. Thank you
×
×
  • Create New...