About kab8609

kab8609 · ‎02-24-2016

Do you have access to your database? Look for this table "sales_flat_order_payment" and then the column ""cc_number_enc" does it have a value like: 0:2:sdf3432432432:423423423==? You will need to unsalt these.

kab8609 · ‎02-24-2016

You need to login to your Magento Connect (from the admin) and insert the key there. On a side note, I would strongly encourage you to put your code in Version Control and import the extension manually. You will have greater control of your site and will result in less errors.

kab8609 · ‎02-24-2016

Most likely because the google sitemap doesn't need to be in https mode for google to use it. You can still gain access to the file in HTTP and HTTPS. The file does technically live outside of Magento.

kab8609 · ‎02-24-2016

I am not sure of what you are trying to ask. Can you describe it in another way, maybe with screenshots?

kab8609 · ‎02-24-2016

You just need to apply the 1.9.2.4 code over your 1.9.2.3 code (assuming you did not edit core files). This is easily done using a version control system. You do not need to get a new SQL db, or a new hosting location. If you applied the latest patch, I wouldn't worry about going over to 1.9.2.4 especially if you are not running PHP 5.3 (which is what this fixed).

kab8609 · ‎02-24-2016

To get Magento running on PHP5.6, there are a few hacks you need to do. Have you done those? Magento 1x currently doesn't support PHP 5.6.

kab8609 · ‎02-23-2016

There was a flaw with the 7405 in which it broke on PHP 5.3. There should be a new security patch out now (SUPEE-7405 v1.1 or CE1.9.2.4) that will fix this issue. https://www.magentocommerce.com/download I have also alerted Meanbee about this post for them to take a look at anything on their side (they are literally one of the best Magento development firms out there). Just something off topic, I would seriously start working towards getting upgraded to at least PHP 5.4. 5.3 is very old and a lot of companies don't even support it right now.

kab8609 · ‎02-23-2016

While I have had a issue similar to yours, it was not a 20-30 minute period daily. It seems like something is failing. Either the connection to the sessions or the place where the sessions are stores. Are you able to monitor uptimes on your servers yourself? Are you able to monitor the server logs yourself?

kab8609 · ‎02-23-2016

Are you using a regular url for unsecure and secure URLs? Are you using HTTPS at all? If this is a clean install of Magento with no changes, then this is coming back to your server setup. Have you tried a more ideal server setup? I don't know of anyone running a local install of Magento on a Windows box.

kab8609 · ‎02-23-2016

What specific version of Magento 1.9 are you on? How are you saving the sessions? What is the lifetime of the sessions? Can you do a diff to make sure all the code is in there and correct (like nothing was hacked)?

kab8609 · ‎02-23-2016

So Magento cannot do that (believe me, multiple top developers have complained about this). I will recommend one of these approaches here to block that out from your diff: https://gist.github.com/brendanfalkowski/7274294 https://gist.github.com/peterjaap/720ebff36062eec584cc There are several different ways on how to do it as well.

kab8609 · ‎02-23-2016

Yeah this is definitely a cron issue. You will want to have your cron run every minute if possible. The setup of the cron depends on your server provider. An example of the setup would look something like this: https://docs.nexcess.net/article/how-to-configure-a-cron-job.html

kab8609 · ‎02-17-2016

I would recommend you have someone examine the code as a first step instead of switching servers. I already assume you know how to minify CSS/JS, enable gzip, caching (make sure you dont have a lot of hole punches), image optimizations, etc. I would have someone look at your setup using Blackfire so you can actually see every process being hit. We did a project on this at the last Magento Imagine Hackathon and our setup is: https://github.com/magento-hackathon/BlackfireMagentoVagrant

kab8609 · ‎02-17-2016

The Inchoo extension is a great starting point, however as others have stated it is a work in progress. I do run M1 on a PHP 5.6 instance and will randomly find a issue here or there. The step up to PHP 7 will probably include even more workarounds. If you do use PHP7, I would recommend you contribute to the Inchoo github page.

kab8609 · ‎02-17-2016

If there is no var/log folder. Then your permissions are not set correctly. If your permissions are not set correctly in var, you will run into issues. Especially with caching. I would examine all your sites permissions. Here is a article to help you out. https://blog.nexcess.net/2010/12/06/securing-magento-file-directory-permissions/ In my opinion, I would personally not use Magento Connect to upgrade your Magento Instance. I would personally do it through version control as you will be able to have more control of your code.

kab8609 · ‎01-12-2016

Hey there, Magento is just the platform it is built on, they have no control over retailers. If you cannot contact them, then I suggest you ask your credit card company to reverse the charge. Magento can not do anything and are not responsible for retailers who use their software.

kab8609 · ‎01-08-2016

I am Kris and I am the Lead Magento Developer for a Fortune 500 company. I am looking forward especially to this Magento Imagine, because this is the first one with a new product and I want to see how the community as a whole is reacting to it. I have been to most Magento Imagines as well as X.Commerce Innovate. When i'm not at a computer, you can find me in the weight room, volunteering painting field lines for local sport teams, or sending countless snapchats to Sherrie (usually of my dog).

kab8609 · ‎12-22-2015

Did you want it to reprocess through the payment gateway as well (for different prices)? Have you tried just editing the order through native Magento? What limitations are you seeing there?

kab8609 · ‎12-11-2015

What do you mean paste into your theme? It is a backup program. Nothing is suppose to be in your theme. Also, just a FYI. Any Magento host would be making nightly backups and scheduled backups are built into Magento in the later versions.

kab8609 · ‎12-11-2015

Magento 1 will not be receiving anymore feature updates, and will only be receiving security updates for the next few years. It is always best practice to make sure you are on the latest version, however in your case you are probably well enough off on 1.7 provided that you regularly check for modified files, logs, and keep the patches up to date. With Magento 2, I would suggest you start taking a look at it, not for something immediate, however for something to migrate to down the road.

kab8609 · ‎12-08-2015

Are you using a older theme or the standard Magento theme? Any core edits? Usually, when you get that error, it is usually because this is missing: <?php echo $this->getBlockHtml('formkey')?>

kab8609 · ‎12-08-2015

Your best solution is to start merging on instance into the other. However, for the time being I would just upload a inventory update CSV on both sites (or even better create a extension that automatically pulls the inventory file and applies it).

kab8609 · ‎12-08-2015

Has your server gone through any recent upgrades? Can you do a diff of your code from your version control system and what is on the server? If this was working perfectly for 2 years, someone must've accidentally changed or deleted files. I am hoping you have applied the required security patches that have been released for the past 2 years.

kab8609 · ‎12-08-2015

If that is the exact same error message you are getting it for any payment gateway, then I would suggest removing the Netgains Stripe extension from your code repo.

kab8609 · ‎12-08-2015

That is a 3rd party extension, can you provide the code to the file? It is impossible to solve without the required information. Can you also provide a description of what that extension is suppose to do?

kab8609 · ‎12-08-2015

Can you provide any screenshots showing where you are looking? Do you see anything in the logs? What version of Magento are you using?

kab8609 · ‎12-08-2015

The patch is more on backend code, not theme code. There is no question that you should apply the patch. If the theme was well written, it shouldn't affect it at all.

kab8609 · ‎12-08-2015

Your first steps would be to revert any changed core files. Remove unrelated code files. Then apply the shoplift patch that was issued several months ago.

kab8609 · ‎12-08-2015

Is your whole repo in that /staging/ folder? Can you elaborate on your problem some more? Error messages (the whole thing)? Is it on a specific part of Magento?

kab8609 · ‎03-26-2015

We need more info then this. Are you seeing errors in your logs? What is the exact error message? Can you post a screenshot? Did you setup the permissions correctly? Have you edited any core code? What extensions are you using?

Re: Processing Saved CC orders

Re: Enhanced Admin Grid extension install

Re: Trouble generating google sitemap

Re: I made my own purchase with a check

Re: Updating from 1.9.2.3 to 1.9.2.4

Re: Security update to 1.9.2.3 and Meanbee Royal M...

Re: Security update to 1.9.2.3 and Meanbee Royal M...

Re: Magento randomly logging out on back end and l...

Re: problem with checkout/onepage/saveBilling

Re: Session file problem

Re: Copyright Update madness

Re: Emails not being received after upgrade to 1.9...

Re: Magento Profiler - Need to speed up the Shop

Re: PHP7

Re: after i upgrade

Re: Información

Re: Introduce Yourself!

Re: Extension that can edit order article, tax, pr...

Re: MageBackup - Backup Solution Lite

Re: Is it a problem to stay on Magento ver. 1.7.0....

Re: Product Review Page Remove from Cart Problem

Re: Two installations with the same inventory

Re: error to my live site

Re: Getting fatal error when clicking checkout

Re: Fatal error: Call to a member function getMeth...

Re: Tracking not working in admin

Re: Virus/hack

Re: Hacked Site/Virus

Re: magento problem HELP

Re: Can not upload any images