In PrestaShop v1.4, you can use arrows just like the products to rearrange categories.
In PrestaShop v1.3 and below, categories are always sorted alphabetically, unless you add a number prefix like this:
01.Category 1
02.Category 2
PrestaShop will use that number to sort the categories, then remove it so that only Category 1 and Category 2 are displayed.
This problem might not exist just with intel motherboards but can be applied to any brand.
I have been running Microsoft Windows Vista Ultimate 64-bit for a couple years now on my Dell Precision with 0 problems. So, naturally I decided it was time to upgrade to Windows 7 Ultimate.
Much to my dismay, after performing a fresh installation of Windows 7 Ultimate 64-bit Edition I found that it was acting very strange. Sometimes it would sit for a few seconds when I did simple things like close a window or open the Start Menu. It was very slow. Furthermore, the hard drive light was always on and the hard drive was always making sounds.
I knew this had to be a driver issue because the machine had worked flawlessly under the heavy pressures of Vista. So I started by flashing the BIOS. That didn’t work. I tried updating my display drivers and that did nothing.
I decided to see if I needed to update the Intel Chipset driver and it turns out that solved everything. Microsoft has done a good job of making sure Windows 7 gets all of the correct drivers during installation as all of my other machines have worked flawlessly.
Download and install Chipset Drivers
Unfortunately, Intel doesn’t have any Windows 7 x64 specific drivers: (maybe not so true now)
However, using the Vista x64 drivers did the trick and everything works great now.
Also check
Also try
There is actually a way to reset the activation period in XP, up to 4 times (120 days). It's not documented very well, no doubt Microsoft don't want it known too much...
{code}rundll32.exe syssetup,SetupOobeBnk{/code}
You can check if it worked by looking In Event Viewer under Application tab, should say you have 30 days to activate.
Solution 1:
This problem is actually listed in the "common problems" section of the installation instructions, but many users only seem to run into it when they start configuring their site after the initial setup. So here we go again:
This is commonly known as the "whitespace problem".
The error message typically looks something like
Warning: Cannot modify header information - headers already sent by (output started at /path/to/geeklog/public_html/config.php:581) in /path/to/geeklog/public_html/system/lib-sessions.php on line 180
(line numbers and file names may vary). The problem is that many editors seem to add additional blanks (spaces) and/or empty lines at the end of a file when you edit it. This so-called whitespace is then sent to the browser when the file is loaded and interferes with the header of a page that Geeklog tries to send to the browser, often causing problems such as login problems.
The fix is, obviously, to remove that whitespace from the file. Read the error message carefully. It says "output started at ..." followed by a file name and a line number. That is the file (and line) that you need to edit. Ignore the second file name - that is only a file that included the file that has the whitespace. The first file is the one you have to edit, not the second one.
Since the editor you've been using caused this problem in the first place, you should use another editor to fix the problem and remove the whitespace. See this and this forum thread for some recommendations for editors to use on Windows. Unix/Linux users can't go wrong with vi.
Taken from here: Cannot modify header information - headers already sent by ... - Geeklog
Solution 2:
This error message is commonly seen by programmers starting to use PHP. Understanding why this error occurs will help find the solution.
PHP handles lots of the work of generating web pages for you, without you even having to ask. A web page is composed of two parts, the header and the body.
The header is generally stuff that you don’t need to worry about, is generated automatically, and contains information about the page, the server, related cookies, and so on. The header information is important, but it is not typically seen by the user. Here are some examples:
Date: Mon, 10 Jul 2006 18:51:59 GMT
Server: Apache/2.2.0 (Unix) mod_ssl/2.2.0 OpenSSL/0.9.7g
Content-Encoding: gzip
Content-Type: text/html
Sometimes programmers want to change some of the header values. For example, if the PHP if generating XML output, the Content-Type should be changed to reflect this. Another common example is in redirecting the user’s browser to a different web page using the Location header element as described in this Tech-Recipe.
The header must come first in the response from a web server and is separated from the body by one blank line. The reason this error occurs is that some part of the body of the web page has been sent to the user already when a request is made to set a header value. Because PHP simplifies many things for you, the problem may be hiding in plain site.
Here are some guidelines for finding the problem: