Jump to content

bsmither

Member
  • Posts

    16,418
  • Joined

  • Last visited

  • Days Won

    533

Everything posted by bsmither

  1. Illegal array key 'cart_lookup' You have a malfunctioning plugin. It is adding '&cart_lookup' (including the apostrophes) to /index.php?_a=vieworder'&cart_lookup'. View Order is a storefront URL where a customer examines past orders. unlink Not to worry. This is just a bit of house keeping - wanting to delete a file that's already been deleted. Invalid argument supplied for foreach() (You may have the wrong log entries. Probably not an issue. The line number suggests this is where a "behind the scenes" (ajax) request for image/file directories to populate the image file pickers in admin. No customer information detected. This is interesting, but may be caused by social media just doing its thing. Invalid Security Token What version of CubeCart and PayPal_Pro are you running. As of CC618 (supposedly), _g=rm is supposed to be "ignored" and not cause CSRF or bad security token errors.
  2. The yellow button is coming from /modules/plugins/PayPal_Pro/images/. You can load it into an image editor, make it larger, save it back, and force the browser to reload it. Or, edit the file /modules/plugins/PayPal_Pro/hooks/class.cubecart.display_basket.alternate.php. Near line 56 is some code that is building an <img> tag. You can add height and width attributes, or style attribute, here to match the button size.
  3. I got this working: https://github.com/garand/sticky
  4. I have yet to install CC621, but a CC620 installation gets me this: <script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script><!-- Right Box #3 content --> <p><ins class="adsbygoogle" data-ad-client="ca-pub-xxxxxxxxxxx" data-ad-format="auto" data-ad-slot="2445020xxx" style="display:block"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script></p> This is after having made the edits to config.js as described earlier. Specifically, the $removeEmpty being switched off. (Since a change has been made to this file, be sure to force your browser to reload it - usually with CTRL-F5.) Note that CKEditor still wants to wrap things in <p></p> tags.
  5. The above solution was for a specific situation (<i> tags used for Font Awesome). Please determine if the technical docs for this "adsbygoogle" require the use of the <ins></ins> tag pair. If not, try using a <div></div> tag pair.
  6. You might want to send an email to CubeCart HQ and verify if you have a support plan. Those with support plans (supposedly) are indicated in the forums with a blue "Premium Member" tag on their name. What has been fixed? Front end CSRF requires call and process exception for payment gateway data https://github.com/cubecart/v6/issues/1601 CSRF token regeneration on each page load damages usability https://github.com/cubecart/v6/issues/1921 Admin login with SSL enabled but standard http protocol fails https://github.com/cubecart/v6/issues/1637
  7. There are three separate parts to a standard PayPal transaction: the customer goes to PayPal, PayPal sends a notice to the store for which CubeCart verifies, and the customer comes back to the store (optional). When the customer comes back to the store (optional), Cubecart has already moved the order to Processing (or kept it at Pending if PayPal says the transaction failed). (Please do not confuse "having completed the transaction" with CubeCart's order status of "Completed" - admin has shipped the product.) CubeCart 6.1.7 has a syntax error in /classes/sanitize.class.php (use your hosting account's control panel tool "File Manager" to view the contents of this file, if curious). Plus, the situation where CSRF Security Alert pops up has (most likely) been fixed. (I say "most likely" because I don't have a PayPal account to test it. Even so, there would be more complaints if it wasn't fixed.) So, what I recommend is that you manually upgrade your site to CC621. If that does not sound appealing to you, then I would recommend at least that you download CC621 to your computer, extract the package, and replace your existing /classes/sanitize.class.php with the newer version. (The forums indicate you are a Premium Member, and as such, should have some sort of support plan in place.)
  8. Please let us know the exact version of CubeCart you are currently using, and the exact name and version of whatever PayPal gateway you are using.
  9. I am going to try this: https://github.com/jbutko/stickyNavbar.js Nope, didn't work very well.
  10. Examining the suggested extension, it seems this is just a simple (non-Foundation) menu thingy. As such, using Foundation's nav-sticky javascript function probably won't work. Also, one would hope the code isn't encoded so that the user can change what information is shown in the menu boxes. There is a CSS "position:sticky" but using that, there is a requirement that there is no "overflow:hidden" in any ancestor node - which there is (hides the shopping basket). So, I'm sure there is a solution, but I do not know what it would be.
  11. Please view the admin, Product Options screens (not where you actually choose the options to assign to the product). There will be a checkbox to make these options required.
  12. There is this: https://www.cubecart.com/extensions/plugins/vertical-navigation-box Are you wanting the nav bar to "stick" to the top of the page as the page is scrolled?
  13. Please create the error_log and let's see what may be the problem.
  14. We would ask that you verify the name of the database as stated in /includes/global.inc.php matches the actual name of the database as seen in your hosting account's control panel (Cpanel?). Also, if the database tables have a prefix, make sure it matches what is given in global.inc.php. Not allowing a table column's name as the "key" to fetch the row's contents usually means the requested table doesn't exist, or CubeCart is using a table prefix when it shouldn't, or v.v.
  15. In the administration folder /sources/settings.index.inc.php: Near line 390, find: 'product_weight_unit' => array('Lb' => $lang['settings']['weight_unit_lb'], 'Kg' => $lang['settings']['weight_unit_kg']), Change to: 'product_weight_unit' => array( 'Lb' => $lang['settings']['weight_unit_lb'], 'Oz' => "Imperial (oz)", 'Kg' => $lang['settings']['weight_unit_kg'], 'g' => "Metric (g)", ), You will need to mention how you do shipping, as most (all) non-USA shippers want to use "kg" as the weight unit.
  16. "custom_oid" has a regular KEY and that's good. At some time, a second occurance of adding a KEY index happened, creating "custom_oid_2". Maybe running the setup script a second time? Anyway, you may delete the "custom_oid_2" index. Lines 806-808 are correct for CC621. The question then becomes, from where did CubeCart get information that the column "custom_oid" is expected to have a UNIQUE KEY.
  17. Provided that the digital file is publically accessible, in admin, Add/Edit Product, Digital tab, Custom File Path section, you may enter either a direct path to a folder on CubeCart's server, or a Full Web Address that points to anywhere on the Internet. If your AWS repository requires a login, that may pose an obstacle unless you know how to overcome it.
  18. According to CC621 /setup/db/upgrade/6.2.1.sql, there is: ALTER TABLE `CubeCart_order_summary` ADD KEY (`custom_oid`); Then, in CC621 (as compared to CC620), in admin /sources/maintenance.index.inc.php, line 808: 'custom_oid' => 'KEY' (was: 'custom_oid' => 'UNIQUE KEY') So, please verify that your admin file /sources/maintenance.index.inc.php, line 808 is correct.
  19. I don't use phpMyAdmin that often, but it should not be difficult to find where to add such an index. On the other hand, if one doesn't use any custom order id indicators, just ignore this.
  20. It is worthwhile to have an INDEX against that column. Just not UNIQUE.
  21. According to the history of this code in the Github, the change to the schema had to be backed out because empty values (or null) would be in multiple rows - and that is not allowed for a UNIQUE column. I suppose what should have happened is that the expected schema description should have been updated to not show any discrepancy.
  22. I supposed you wanted to show this on the Latest Products area, or a category or search results listing (where $product - lowercase - is used).
  23. Good to see these results. I cannot speak to mod_security (start up a conversation with a pro web-hosting provider for that), but I should add this to my litany of questions to ask when someone makes a forum post: "It don't work!" "Has your host installed some sort of security package on your site?" As for "no telling what legitimate text is going to base64 encode into banned words," there are only two (as far as I can tell) instances where base64 encoded values are used: in SQL queries reading from and writing to the database (CubeCart_config and (for some versions of CubeCart) CubeCart_code_snippet tables), and when POSTing Code Snippet code (for some versions of CubeCart - admin, Manage Hooks, Code Snippets tab). (As I see it) So, for CC6114, the Code Snippet code text edit area in the admin skin template, no longer converts the textarea contents to base64 so that it survives the POSTing. I am concluding, therefore, that "attempts to hide badness in base64 encoded strings" is not exactly what is happening here.
  24. Please confirm if there is, or is not, a UNIQUE index (key) on the "name" column. If there is, then remove it. (I say there cannot be this UNIQUE index, because there being two rows with the same value has already violated that schema restriction.)
×
×
  • Create New...