Jump to content

intimi

Members
  • Posts

    10
  • Joined

  • Last visited

About intimi

  • Birthday 07/19/1954

Profile Information

  • Location
    Kortrijk, Belgium
  • Activity
    User/Merchant

Recent Profile Visitors

2,517,348 profile views

intimi's Achievements

Newbie

Newbie (1/14)

6

Reputation

  1. No, I just put all the subcategories plain in the "left side" menu, as a workaround. I haven't looked for a template that should display the content yet. Maybe the problem is that a template for cms categories is missing. I'm not good enoug at it to edit something that's missing. ;-) The data is there, but no page, so this might be a clue. It also does not display the content of the CMS category page, so, if customers are supposed to see the general conditions to round up an order, they get an empty page. :-(
  2. There's something unfresh about CMS too. I had put all the details like privacy, delivery, shipping, payment, returning goods, refunds etc... under one category "Terms and Conditions", and with the right configuration of the module "C M S Block" it worked fine for 1.5.2 In 1.5.3, the CMS categories all return "This page does not exist." - I uninstalled and reinstalled the module, the same shit happens. - I created a new category with some subcategories, and configured them right. The newly category shows up in the left nav bar, but clicking on it also shows the same error message. As there's no clear error message, I have a hard time finding out what's up here. Yet another bug? :-(
  3. There's something unfresh about CMS categories too. http://www.prestashop.com/forums/topic/213456-cms-categories-bug-in-153/
  4. Something to be avoided in the future: Someone added a beautiful new function but forgot the instructions to upgrade the DB as well. That's a pretty common mistake as the DB is not a part of the versioning system and many developers leave DB design to the well encapsulated realm of a DBA. In enterprise environments, this is often a bless. ;-) On the developer's platform, it will all have worked well, as he/she added these needed colums manually. Unit testing would be well on it's place here! (If it exists on a dev platform, I appologize.) That means that, for each and every module, controller, function or whatever, a so called unit test should exist. When a change is made, the unit test should be examined that it checks the impact of the change as well. The idea is that for a given input, ther must always be the same output. It's a good idea to split up complex tests in a series of simple ones: a little change requires only to change or add a simple test. Complex tests would make the testing itself error prone. These tests are bundled in a test scenario that should run periodically, as even data changes in a live system always can create unexpected conditions. In some environments I have seen, there is a "main" and a "test" part, the test part's structure being a kind of an echo of the main structure. This made it easy to leave the test part out of the operatonal environment, while it remained easy for developers to find or create the appriopriate tests for their changes. For testing against a live thing and the impact of user input, it's essential to have all the testing on board, however.
  5. - BS? Not really if you use the recent 1-click upgrade module. It has a rollback function. Select a backup version and click. - I don't like those workarounds either: what if they simply had omitted all new columns in all tables? It could take us a century to find out. So I expect another minor "stable" upgrade within days, now. - What users could do is run PS on an operational server, AND install it on a small, cheap server too, just for testing. Always do upgrades in your test environments first. Copy DB from operational to testing environment before doing the upgrade, so you're a bit more sure you will get operationally what you see in test. - Sticking to old versions too long is much like trying to get a university degree without attending courses: after a couple of major upgrades, it's like you are the only english speaker left over in mainland China ;-)
  6. @THM11 - I had some weird behaviour in my navigation due to a cached JavaScript. It simply went away after clearing cache in all browsers on our PCs. - I assume that CSS might be cached much the same way as JS. Do you use some third party caching solution? (like CloudCache or so) I wouldn't know how to clear cache that is stored on servers along the way.
  7. Now I can create or modify all sections, including shipping, prices, seo, combinations, associations, suppliers,... The problem appears to be solved for me, but I cannot guarantee that there will be no probs further on.
  8. I had the following msg: "An error occurred while updating object. product ()" I found a solution after I edited in prestadhop/config/defines.inc.php to temporarily change this line define('_PS_MODE_DEV_', false); to define('_PS_MODE_DEV_', true); So that revealed that the field redirect_type was missing in the tables ps_product AND ps_product_shop I know this is naive and optimistic, but adding it as an INT field which may be left empty to both tables did the job for me. Problem temporarily and dirtily solved. SO PLEASE, IF SOMEONE AT "THE FORGE" CAN TEST THIS OUT THOROUGHLY AS THIS DOESN'T FEEL REALLY SAFE. Regards and best wishes, Michiel
  9. RESOLVED. It was apparently a caching problem. Cleaning the cache, cookies and "data of hosted apps" under History of Google Chrome did the job.
  10. Backoffice -> Catalog -> Products -> [choose any product] -> [change to, for instance, associations]: The upgrade from 1.5.2 to 1.5.3 worked flawlessly but when I try to update a product and click on any other tabs than the main info page in the left column, like associations, price, combinations or shipping, the url is adapted, but always the same main info page is reloaded. Does anyone else have this problem with the backoffice of 1.5.3 ? UPDATE: maybe inspect element -> console can make me wiser? admin-products.js : line 781: Uncaught ReferenceError... if ($('#active_on').prop('checked')) { showRedirectProductOptions(false); // that's line 781 Uncaught ReferenceError: showRedirectProductOptions is not defined showRedirectProductSelectOptions(false); } else showRedirectProductOptions(true);
×
×
  • Create New...