Jump to content

Noodleman

Member
  • Posts

    728
  • Joined

  • Last visited

  • Days Won

    28

Everything posted by Noodleman

  1. looks like the issue may be related to using an unsupported web server, use Apache as it's the only officially supported web server and in your own tests, seems to work fine.
  2. definately a web server issue. try this: https://www.litespeedtech.com/support/forum/threads/solved-err_spdy_protocol_error-after-121-seconds.14679/ It could be hitting a timeout value, thus 500 error.
  3. in your initial post you said "it eventually times out with a http 500 error". can you attach a screen shot of the screen where you see that error? If you have the ability, restart your database server service and web server service. If you have a hung query/thread this will free it. if you are getting a 500 error, I would expect to see this in your error logs. Check your web server error log as well as the PHP error log. In theory, yes it could be litespeed. I've seen some sites perform badly when using fCGI, no reason to think it couldn't be a similar issue. Apache is the only officially supported web server: https://www.cubecart.com/hosting-requirements
  4. ok, so the errors you've provided from the error log are old and already resolved? What are the latest items from the error log after you've solved that issue. Since PHP 5.4 was just a test, What version of PHP are you actually settling on? delete/remove your error log, try and login again and then post the entire error log here. Some steps to try: 1) Manually delete the cache on the server (sometimes works, but don't think it will in this case) 2) It could be your image cache rebuilding, in which case it will require several attempts to login before it will "just work". to test if this is the issue, rename your image directory, then add a new image directory with no images in it. Can you log in? (put it back after the test)
  5. Why are you using PHP 5.4? You want to be using AT LEAST PHP 5.6. anything prior to PHP 5.6 is insecure. http://php.net/supported-versions.php Your PHp version is missing libraries, in this case you need top install the PHP Multibyte string functions into PHP.
  6. definately some server side oddities. what version of PHP is your server using?
  7. I checked it for you this morning, it looks OK, so I assume you fixed the issue?
  8. For reference: https://support.cubecart.com/index.php?/Knowledgebase/Article/View/203/46/how-can-i-create-a-plugin-using-the-code-hooks-system-in-cubecart-v5 The concept is pretty much the same for a snippit, although you just paste your code rather than build a module
  9. Hi Henry, I just replied to your ticket. I am hoping to get to this in the next few days. being realistic, Monday or Tuesday.
  10. You are probably going to need to have that PHP code output to a smarty variable using a code snippit or hook. You can merge the contact-form-run.php file contents with your PHP code. Then, all you need in your document is the smarty variable, something like {$MY_VARIABLE} The complexity really depends on what is in your PHP files you are including.
  11. smarty is PHP, but written a little differently. what is the code you need to add and why do you need to add it?
  12. it depends on the code, you can normally do what you want using smarty rather than directy PHP. Enable parse smarty tags for your document.
  13. Following up on this thread. I finally got it all figured out. Thank you. I used the approach that Al suggested and built on it with a bunch of other functionality.
  14. What version of cubecart are you using? I thought this was resolved some time ago
  15. PHP 5.4 is very old, you should consider updating it to at least PHP 5.6. However, try the attached file. it's a version of the module encoded for earier releases of IonCube. simply replace the existing module directory with the one inside the ZIP file. If it doesn't work you can rename/delete the module. Let me know the outcome. There are other versions I can provide if this one doesn't do the trick 1.0.1-LEGACY_google_merchant_bulk_category_assign.zip
  16. Good Morning, @Al Brookbanks is correct. The most common reason for this issue is that your web server does not have IonCube loaders installed, or the version of IonCube loaders installed is old and not compatible with the current versions of IonCube. Firstly, to gain access to your store admin area. Use FTP to connect to your server, navigate to the /modules/plugins/ directory and rename or delete the folder called google_merchant_bulk_category_assign. This prevents the module from being called and means you can use the store as normal. Next, click on "PHP Info" from the admin menu and let me know what version of PHP you have installed. It's possible you have installed the PHP 5.5 version of the module and are using PHP 5.6 or vice versa. I make two downloads of each module available based on the PHP version you are using (5.5 and lower or 5.6 and above). Next, search using your browser within the php info page (CTRL + F) for the word "ioncube". If you find any matches, ionCube is installed but likely outdated. Find the section where it provides the version number of ionCube and let me know what it is. I can send you a version of the module which will work with your server settings. If IonCube is missing it will need to be installed.
  17. drop the "Setup" directory into your store from the CubeCart zip, then run setup. it's got a step to validate all folder permissions. You can get to this step then just close the tab and delete setup directory.
  18. since it's not mechanical you don't have the seek time to find the sector, much quicker IO (recommend M.2) the only concern with your setup is the loss of power to the storage and it not being unmounted correctly. based onthe storage limits, why not just get a 256GB USB stick so it's self powered?
  19. You might find it better to use a large USB drive instead of an SSD. The hub itself could be a factor. When the power drops to the hub (car restart etc) it's the same as unplugging the USB device, and plugging it back in again. This is likely causing your table to scan the media on the storage device as it's plugged in and is the main factor of the delay. if that statement is true when the NTFS drive is full you should see similar behaviour. you really want a storage device that's always on. because the drive isn't being "safely" powered off/unplugged it may be marking the file system on the drive as unclean, so it's doing a file system check when it powers back on. this happens a lot on FAT systems, but it also happens on NTFS. NTFS really doesn't like being unplugged in this way and typically you may run into more corruptions /issues due to it over time
  20. NTFS is a more advanced file system, it stores it's indexes in a different method to FAT based systems. f.y.i, you can manage partitions in windows using "Disk Manager", inclusing hidden partitions. assuming windows knows how to read the file system on the HDD. It can probably read this file system faster because it's more advanced / indexed better. The real test would be to make the SSD NTFS and validate the issue isn't something firmware related with the SSD itself. you should just be able to adjust the mount command being used for your media to the specific partition you want to use, the hidden one should be irrelevent in that context. In a table, when the SD/HDD is plugged in it does a scan of the drive. this takes a little time. it could be this that you are running into issues with. Assuming your HDD is powered from the tablet itself then it shouldn't need to cycle.
  21. That sounds more appropriate. I think it's an excellent idea.
  22. Here's the breakdown of the issue. Indexes are being used and are improving performance to the level you are reporting. without them it would be much worse. The SQL query we are focused on derives the quantity for each product, then sorts by that quantity. this is an expensive query. There isn't much that can be done to improve this SQL query. @Al Brookbanks, this may be a candidate for an improvement. The queries probably shouldn't run on page load in this case, but perhaps on demand via a "refresh stats" button on the statistics page. This can then run the queries, gather the results from each and store the results in a database statistics table. the reports can then pull the derived values from the table rather than calculate it every time. This isn't too much of an issue as it's only going to impact stores with a large data set.
  23. You were in the right place for the queries. would you be willing to let me take a look at it directly?
×
×
  • Create New...