What are
/r/Magento's
favorite Products & Services?
From 3.5 billion Reddit comments
The most popular Services mentioned in /r/Magento:
Adobe Commerce
Snipboard
PHP
Stripe
elasticsearch
Cart2Cart
Stack Overflow
PageSpeed Insights
Server Fault
Laracasts
Amazon Web Services
GTmetrix
Algolia
Apache HTTP Server
SlideShare
The most popular reviews in /r/Magento:
https://magento.com/blog/magento-news/ongoing-magento-1-support
The official policy from Magento is that they will provide formal notice 18 months in advance of end-of-life.
I work for a partner agency, and I’ve heard a lot of misinformation about this, so I asked our partner manager, and he said that we should be receiving an update very soon. My best guess is that all Magento 1 support will end officially in June 2020. Sup /u/thatben?
If you’re starting an Magento build today, use M2. Magento is M2 now.
We use SendGrid for transactional email. The message search lets you troubleshoot email delivery problems. The activity logging shows who has opened or clicked on a link in a message. They also offer dedicated IPs which further help with delivery.
Mageno Enterprise Cloud Edition on AWS.
Side note: /u/alanstorm has answered at least 1,200 of my questions on stackoverflow – never expected to answer one of his, ha.
'We discovered that the site was not designed to be 'responsive'. This sentence really sticks out. Did you not notice this during the development phase? Did you only notice this at the end?
It indicates perhaps some bigger issues than just the developer involved.
I think also, it might be worth reading this: https://medium.com/programming-ideas-tutorial-and-experience/506a06ae35ea.
Anyway, good luck with your search, but remember a developer can only ever be as good as his customer and you need to be as engaged in the development of your web property as you expect the developer to be.
The last time I installed Magento I followed this guide:
I generally rate the DigitalOcean guides.
I don't really know about composer, but you should be able to install a new copy of Magento under a different directory / hostname and pointed to a different database schema without clashes.
But having said that, I normally spin up a new VM guest each time so I know I'm starting clean.
You have to create 301 redirects (https://moz.com/learn/seo/redirection) for old URLs asap. Otherwise customers landing on them via Google / bookmarks / shared URLs will see 404 page. This can cause a great decline in sales.
You can either create redirects within Magento or on server level (apache / nginx), that does not matter, but you gotta do it! I hope you have old URLs available and product number is not too big - in that case you can do it all manually. Good luck!
Just set up a cron to see if the data needs to be reindexed, if it does, then index it. I wrote this a while back. It's meant to be procedural and not in a loop or anything.
I believe originally we ran that file at 2am EST, since then, we've broken up the indexes during different parts of the night due to the customer's POS maintaining inventory and pricing through the Magento API.
The indexes themselves shouldn't have any direct effect on SEO at all. As long as the indexes are up to date, google will spider the site and have the correct info for each product/page.
class CraftyClicksValidate_AjaxController extends Mage_Core_Controller_Front_Action{
public function indexAction() { echo 'respect my autoritah'; $order_id = Mage::getSingleton('checkout/session')->getLastRealOrderId(); //$_GET["order_id"]; $order = Mage::getSingleton('sales/order')->loadByIncrementId($order_id); $shippingAddress = Mage::getModel('sales/order_address')->load($order->shipping_address_id); print_r($shippingAddress); }
What's with the dead|debug code / funny comments? You should clean it up, some other random echos about as well in controller code.
Maybe look at json_encode for returning data for AJAX? In a Magento way Mage::helper('core')->jsonEncode()
I would highly recommend Algolia search. We never bother with Magento's in built search, it's abysmal. The service is well priced (usually free for most shops if you're happy to display their logo) and they have an excellent Magento extensions for M1 and M2.
Their search engine is phenomenally fast (instant search returns results as you type with usually less than 20ms latency on the results request being complete), accurate and works nicely with Magento attributes.
set reply-to to NO covers the issue in Magento 1 or 2
With this background you should probably consider checking Magento University - https://magento.com/training/catalog/merchants-marketers
Start from merchant/marketer track. There are free and paid courses there, even paid on demand are not crazy expensive.
I've been experimenting with Docker a lot. We're trying to come up with a dev-to-prod pipeline using containers. The goal is a little different from someone who wants to sit down and start hacking on a Magento extension, throw it on GitHub and work on something else. While you can pretty much do that with my Magento-oriented php stack Docker images, it's not easier than Vagrant in that respect. On the other hand we now have these complete images of fully-configured Magento instances with specific snapshots of the database and our extension. It's now really easy to reproduce defects and even do combinatoric configuration testing by swapping database containers.
You can do crazy things with Docker – we don't need ~any~ of the php toolchain on our local workstations anymore. PHPUnit, MD, LOC, even Jenkins are all containerized. We can switch the entire toolchain by using a different image tag.
Full disclosure: I work for Linode Support.
Not sure which email address you tried to reach us at, but if you sent something to , it might take a long time to get a response given our current ticket volume. Not making any excuses for the response time on the email you're seeing, though we do prioritize service-affecting issues reported by customers. If you sent the email to a different address, let me know and I'll make sure we look into it.
Given what you're looking for, we do offer a Managed service which seems to fit the kind of basic incident response you're looking for, but it costs $100 per Linode on your account which would take you beyond your budget.
Otherwise if you have general questions, feel free to ask them here, or give us a call — we have 24/7 phone support which will connect you to the same people who would answer your tickets as a customer.
As a dev, I would really love to see some improvement here. Even the /help/documentation page doesn't offer easily navigable information (hard link throughs, no search... list goes on) - really encourage you to check out https://readthedocs.org/ as M2 is OSS.
Run your site through GTmetrix. Look for performance issues especially on your product list and checkout pages. A slow website will make even the best content seem dismissable.
GTmetrix will give you suggestions on how to speed up your website for each problem making your site slow.
I definitely wouldn't count on upgrading being easy. I read in an article that at the very least, all modules/extensions will not be compatible. I can't find the article but I know it was on the front page somewhere for this query.
I really hope that the way of referencing models will be compatible with IDE code completion. Either that, or actually have a useful API doc system. The current one isn't too helpful, I find myself just searching for the model on my local instead. What a hassle!
Multiple database support is definitely something they are working towards. (Again, quoting the ghost article that I misplaced)
What I'm most impressed with is that from the start they are pushing unit testing and code coverage. That alone is worth the upgrade, IMO.
edit: this seems to suggest that Mage 1.6 actually has multi-db support.. I'm skeptical though. Perhaps they just provide the abstraction and it's up to the developer to create db-specific code?
> It's insulting that you say new users don't know what they're doing
Its insulting that you find that insulting. I mean really.
>So don't say people don't know what they're doing just because they disagree with you.
I didnt say people dont know what they are doing. I said new users dont know what they are doing. Why? Because if they did know what they were doing then we wouldn't be calling them new users, now, would we?
New:
>unfamiliar or strange (often followed by to): >ideas new to us; to visit new lands.
http://www.dictionary.com/browse/new
The backend limitations of Wordpress alone make it a sub-par choice to a robust platform like Magento that was initially designed to handle large amounts of data and tables. Thats why you see midsize to extremely large well developed ecommerce sites on Magento. Not Wordpress.
On the security front. I wouldnt trust my financial well being, my family, my business and sales to Wordpress and you shouldnt either. Its the most targeted and hacked platform in the world.
>Though you can be optimistic for the future: I'm sure that Magento being taken over by a private equity firm is a sign of great product innovation to come.
Yes. Magento 2 is very promising and coming along quite well and you really did just fail at every point you tried to make.
The facts are. Wordpress and Woocommerce should be fine for small business those just starting out and those who have no real plans to expand in the foreseeable future. For those that are serious and looking to grow their business and catalog. Those who need room to expand and plan on growing their small business to a large business.
Magento > Wordpress. Hands down.
Most of the largest ecommerce sites in the world dont run Wordpress. They run Magento.
Do you understand the role of classes in programming? Are you handy with a debugger? If not, don't plan on doing anything more than styling changes.
Magento is very powerful but that power comes with a high level of complexity. You need to have some solid programming fundamentals if you're looking to do custom development. Even the design can be frustrating, with xml files controlling so much of the layout.
Mostly, you need to know what you want Magento to do. If you haven't already, find a website that does everything you want your website to do (or as close as you can get). Compare that to the default Magento install and make a list of every customization you need. That should help you figure out how much work you have ahead of you.
https://www.elastic.co/guide/en/elasticsearch/reference/current/windows.html
Basic licence, follow the steps in the gui guide.
It's got the cmd info to start and stop elasticsearch on the same page.
Amazon Web Services give you a micro EC2 instance (basically a VPS) free for a year as part of their 'free tier' (https://aws.amazon.com/free/) - might be something to look at..
Just setup a LAMP stack (they might even have a template for this) and you're good to go.
Try using simplexml for your output using asXML($file), just load the xml into a simplexml object first by passing it to the constructor. $simplexml = new SimpleXMLElement($xml); $simplexml->asXML('filename'); should do the trick.
you can read Magento case studies of one of MSI first early adopters TOUS Poland - https://magento.com/case-studies/omnichannel-tous
Here is a webinar hosted by guys from Strix agency who run the website for TOUS - https://www.youtube.com/watch?v=_2kyUbwFlK0
It should also be noted that 2.2.7 was released yesterday, via https://magento.com/tech-resources/download
"We are pleased to present Magento Open Source 2.2.7. This release addresses critical security issues that include remote code execution, cross-site scripting, and cross-site request forgery issues. Functional fixes include enhancements that focus on wish list and shipping features.
Check out the 150+ community contributions, too. We strongly recommend that all merchants upgrade as soon as possible. See Magento Open Source 2.2.7 Release Notes for more information."
I would respectfully challenge that November 18, 2018 EOL date:
https://magento.com/blog/magento-news/ongoing-magento-1-support (from May 2017, mentions at least 18 months notice).
And who knows what Adobe's gonna do…
It's right on the page you linked??
https://magento.com/tech-resources/download?_ga=1.103959299.2047507671.1486578699#download1971
Short version.
Not Dead.
Just got investment https://magento.com/press-room/press-releases/magento-commerce-receives-investment-hillhouse-capital-accelerate-global
Personally better to 'own' your platform and have full control but it comes down to your own processes, integrations, syncs, etc. We'd normally do a workshop to establish how the business runs and then match an approach/platform to that. The devil is in the detail... e.g. your orders may go to another system, but how, in what format, what frequency, does the other end expect certain things etc. This is especially important for accounting or fulfilment house sync.
From what you've mentioned, Magento would fit the bill. You could use cart2cart to help with the migration and keep that cost low but you WILL likely have lots of manual work to do going over your products and categories regardless of what platform you move to.
There is far more involved but if this helps then great. For a deeper level of detail or certainty customers would usually do the workshop with us or get some consulting from a nearby magento agency. It's a paid bit of work, but you're paying to reduce the risk of making a far more costly mistake when you get stuck down the road. It seems as if you're trying to do risk mitigation yourself right now so at least you're on the right path.
Final note, magento needs ongoing support. Probably a factor more costly than your currently 'settled' oscommerce so you should ensure you budget well for that too.
Hope that helps.
Yup, Magento is a bit of a beast. Much different to WordPress - much more configurable, and code base is more abstracted (including themes). Will take you a while to work out where stuff is, but documentation online is much better these days!
Highly recommend paying (or getting your employer to pay) for the Magento U videos offered (see https://magento.com/training/catalog/developers): this is how we get new Magento developers up to speed and have found them really good!
Also recommend you sign up to a Magento Meetup (see http://www.meetup.com/pro/magento/ as Magento has started centralising where these are listed. If you can't see one locally, search on Meetup.com more generally!).
Edit: see also magentotherightway.com, and look up Alan Storm and Vinai Kopp's blogs for more detailed info on Magento dev too.
Good luck!
[Edited URL to fix, from comment below]
I think the bigger problem was the information publicly posted here a week ago. While I agree that this post shouldn't have been made, mykehsd does have a point below that there hasn't been any good communication. Who was supposed to receive this email? Just partners? What about EE customers? We've just been sitting here in the dark waiting for the patch to be released, or for people to find the vulnerabilities it addresses.
I would second the idea of using a WAF. Stop the Bots before they get to your service. Look into https://www.cloudflare.com/waf/
If you’re worried about too many session files you can look into Redis Session Caching. https://devdocs.magento.com/guides/v2.3/config-guide/redis/redis-session.html
You can configure it to not set session data for bots or limit the bot session time.
Let me chime in here, because I was actually exactly where you were at a 1 year and 2 months ago.
If you've just graduated university/college and this is your first year, then you're where I was. I had no php experience, I had 1 year ofHtml/CSS/JS experience and 6 years of Java development.
If you don't know PHP: https://www.codecademy.com/
If you don't know MVC: https://laracasts.com/
If you don't know Magento. Get ready for the upcoming nightmare.
In my time, I royally fucked up one installation (my first), and have now successfully deployed 5 stores (~100,000 skus total, ~3.5million customers total per day).
In terms of local development. "simple magento vagrant" is the easiest way to get into LOCAL development, learn how to use Vagrant/Virtualbox.
In terms of deploying, LEARN GIT. LEARN GIT. LEARN GIT. I can't repeat this enough. Deploy via git pull.
In terms of IDE. I used to use Dreamweaver. It sucks. Dont use it. Use PHPstorm like everyone is recommending.
If you have a questions feel free to PM me. Also, IRC is your friend. They guys on there are really friendly, and if you are willing to learn, they are more than willing to help.
Required or not? Is the option in the same place on every product? Use css or /and Jquery to hide the option from the customer until you have it back in stock. A simple and quick solution. Drop the js/css in a widget and place it on the product page bottom thru the widget interface.
Link below will get you started in the right path.
http://stackoverflow.com/questions/18300803/javascript-solution-for-hiding-dropdown-list-options
http://jsbin.com/iHIrAQE/5/edit?html,js,output
When helium comes back in stock simply disable the static block/widget. Clear your cache and refresh. Using this solution will save you a headache from messing with your attributes, import files and all that and allow you to instantly re-enable the option once its back in stock. You could even add a prepend/append to it and have a "Helium currently out of stock" message or whatever.
If you need help I could do this in under an hour.
I would suggest you first try to design/map out the data structure. This would be a good indicator whether you should stick with a normalized table structure or use a more flexible datastore. This should become pretty self evident if you start to question or be unsure of how you'll manage to adapt the structure in the future as you add more functionality to the application.
If you end up deciding on a flexible structure, I would highly suggest you give PosgreSQL consideration. With the latest 9.4 release they've introduced the JSONB data type. Pgsql has had a JSON data type for some time now but this new type that supports faster processing and indexing of the data within the object.
You can read more about it from their documentation: http://www.postgresql.org/docs/9.4/static/datatype-json.html
Some benchmarks comparing MongoDB vs Postgres JSBONB on a single instance with 10 million rows: http://blogs.enterprisedb.com/2014/09/24/postgres-outperforms-mongodb-and-ushers-in-new-developer-reality/
I personally haven't had a chance to use JSONB yet but seems like a good choice for when you want to keep your some of your data normalized and other parts less strictly defined. The ability to be able index, query and JOIN on the data also is very enticing.
You can do the same thing with http://www.addshoppers.com and http://www.schema.org/Product but you get better analytics and you can incentivize more sharing.
Full disclosure: This is my startup.
<3
I once tried selenium. But it took too much time to implement and I didn't got paid for it so I stopped working on it.
What I learned from my implementation..
- don't overdo it.. don't visit the login page and enter the form details.. just directly post hardcoded values to a hardcoded url.. this speeds up the testruntime and saves time for writing the test.
- Also, if you need to set attribute values in the backend I would do it by sql and reset the database before each run. (same reason as above)
It would be great if someone writes a standard library for testing magento - where stuff like login into frontend/backend, browse to product, browse to cart, get product-price, get cart price.. is already implemented.
Hoozah, now you know exactly where the error is, on line 80. More specificly there is a misplaced {. You suspect the Exception, try reading up on how to use them: http://php.net/manual/en/language.exceptions.php
That’s weird... We are on M1, also hosted with Nexcess and using their Safe Harbor program. We are currently not using Braintree for payments. But I spoken to them earlier this year about starting to use them and they didn’t have a problem. So I would call your rep and see what they say. You also might be interested in this link: https://stripe.com/docs/plugins/magento/magento1-managed-hosting
Whatever happens, let us know how you go.
I must have done a bad job explaining this. We have uploaded all the pieces with multiple categories and it works fine. I'm just trying to add one new category to a bunch of products.
So to add a new category (421) onto all of their existing ones.
Usually when I re-upload spreadsheets with new categories it overtakes the old existing ones.
I think this link is a solution (still not sure though): https://stackoverflow.com/questions/6491548/programatically-add-magento-products-to-categories
What others said plus:
- every user that lands on your site has about 3 seconds to make a decision to stay on the site or not. The earlier you give them the most important information about the site the better.
That's where the "Above the fold" comes from.
Just imagine - you go to google, type in search bar "truck with big wheels" and click on the topmost / first search result.
You land on the page and there is NOTHING ON THE PAGE WITH "TRUCK WITH BIG WHEELS"!!! AAAAAAAAAAAAAAAA!!! And only small mention of "truck with big wheels" somewhere at the bottom of the page.
^^^ that's the problem you are trying to solve.
There is also the scrolling problem - over last 10 years I worked in E-commerce looking at the heatmaps - they do not lie - only about 10-20% of users that land on your site will scroll all the way down.
So your site better have the most important stuff at the top.
Elasticsearch open source going away is news to me. I'm under the impression it is no longer Open Source meaning the code isn't available for viewing. However, there is still a free version. unless I'm missing something this doesn't seem to impact Magento.
I'm hopeful we'll see some good solutions come out of it :)
The real challenge here is the database interaction.
The choices I see are:
- mock the Mage::... methods
- actually do analysis on the code and do DI (e.g. scan for all uses of Mage::getModel or similar and replace those with methods passed into the constructor).
The first implements patterns we were hoping to get rid of in Mage 2, so I'm opposed to it for obvious reasons. The second loses the benefits of things like service contracts which we should be aiming to implement in new Mage 2 modules. This is still doable with some downfalls, but it seems like a lot more work than $5k, even if this was a flat out contract that eBay was paying a partner (or even freelancer) for and not just a contest.
Someone could definitely generate interfaces based on the exact existing implementation, but it might capture internal methods that aren't necessary and would be much better done manually.
Edit: For anyone interested in trying this, check out http://php.net/manual/en/function.token-get-all.php
FYI: many agencies claim they can fix SEO / site issues. Out of all of the companies I worked with maybe 10% can actually deliver(best ones charge $300 / hour). Most agencies don't care if you succeed - they pump you up about possibility of success and dump you at the end of the contract.
The SEO issues are more complex and you don't see results of the work for a while.
Install Hotjar on your site and start recording heatmaps and sessions. You will start seeing patterns in behavior. If you are not a developer / UX / UI specialist those recordings might not mean much to you, but every recording is a pattern and you can fix a lot of issues by seeing behavior of your users.
The BEST way to find out about the issues on your site is to ASK YOUR USERS!
Hotjar can do surveys - run an open ended question survey for 3-4 months on your site and get feedback. Questions like:
- are you having any challenges on our site? (if user stays on the page for a long time (2-3 minutes))
- what made you buy from us? (put it on success page of the order)
- how can we improve our site?
You will be able to solve site issues faster than any agency can.
Absolutely not. You need to version control. In the ideal world, you have 4 separate code spaces:
- Production (Pulls Only, Weekly Updates with changelogs)
- QA (Beta testing, Pulls Only, Features as they're completed)
- Dev (Your production-esque environment that should imitate QA and Production)
- Local: (A vagrant/virtualbox setup on your own machine for your own testing purposes)
If you're boss/company wants good work, get them to do this.
Check out https://www.digitalocean.com/ for simple dev servers that your boss should be willing to pay for. If they're unwilling, find a new company. You need to be able to do your job well.
Think about it this way...if you scale up, and you will if you code well in the right markets, then you will have to hire new devs. Having the procedures in place and being disciplined in your Version Controlling will make your life infinitely easier.
Setting session.gc_probability will not work, because PHP can't clean up /u/stellaaah's sessions.
As you mentioned, in Debian, and systems based on it such as Ubuntu, sessions aren't garbage collected. Instead, there's a cron job that cleans them up from the default session location that runs as root. This cron job doesn't know about Magento's session location, so any Magento sessions aren't cleaned up.
In these systems, PHP doesn't actually have access to the session directory, only the session files themselves. This is done to prevent folks on shared hosting environments from accessing other sites' sessions, and to make it harder for a site to hijack its own sessions: because PHP doesn't have access to the directory, an attacker needs to know a session ID in order to be able to hijack it.
Also, if I'm not mistaken, the Magento session location isn't specified in php.ini, and this means PHP won't know about var/session either at the time it garbage collects.
All of this means that PHP is unable to clean up its own sessions, so OP will need to figure out a way to clean them up for it. As far as I know, the only two ways are to do it by hand every once in a while, or set up a cron job for root to do it automatically.
Interesting info. Homepage is not a problem with Luma, but this issue is specifically for product page images.
I'm just flabbergasted this issue seems not existent for current Luma users, and that a fix seems hard to find.
In theory, what steps should I take to remove the issue visible here: https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fmagento2demo.firemultimedia.nl%2Fbreathe-easy-tank.html&tab=mobile
Sorry for asking but Im pretty much clueless now. It should be a matter of one line of code in a file somewhere, or not?
I think this is what you're looking for:
https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-install.html
pretty much this: https://aws.amazon.com/quickstart/
normally, and somebody correct me if I'm wrong, but usually you find a merchant that has an API service. With the api you can call the same endpoints whether its the magento site or a POS device. So the magento extension would create its own API calls, and your POS would send separate calls. Most merchants will give you code examples in multiple languages
If you're confident in your coding ability, I would recommend a small amount of custom code that would do this for you.
Create a new module with a config.xml and an observer model (Remember, never modify core). Have a function in the observer fire off on the sales_order_save_before event. With this event, you should have access to the order object.
You can compare the _data array with the _origData array and look for the field "state", which is your order state. If the state from the _data array is "processing" and the state from _origData is "complete" or "cancelled", you can send an alert.
A simple solution would just be to use PHP's built in mail functionality (http://php.net/manual/en/function.mail.php), but if you want to format it nicely and specify the template you can always go through Magento (something like this: http://www.pixafy.com/blog/2013/04/sending-emails-programmatically-in-magento/)
Apologies for any errors, I don't have my IDE in front of me so I'm doing this all from memory.
Edit: Knew I would mess something up. Changed catalog_product_save_before to sales_order_save_before.
You can’t install Algolia. Algolia is a SaaS that you integrate with via their API. They also have a Magento extension. Algolia Magento Quick Start
There is no service from us - the hosted service is from Algolia. The Fontis Algolia extension is a direct connector between their service and your Magento store.
Do yourself and company a favor. Outsource that crap =-p
http://www.shopping-cart-migration.com/
If you manually setup the category structure, attributes then usually its as simple as exporting & importing your products.
If you arent upgrading or changing your Magento core you can just clone your current installation to a dev, install the theme and workout any bugs (depending on your install).
I have a lot experience designing/building stores on Ultimo if you ever need any help. Shoot me a msg.
You can try Cart2Cart to upgrade your Magento EE 1.12 to 1.14 automatically. Time of migration depends on an amount of entities in your store and can be calculated approximately with the help of online estimator. You can find more detailed information here
Here is an infographic with alternatives to Magento Go - Bigcommerce, Shopify, Magento CE, PrestaShop and WooCommerce. Probably it will help to make a right choice - What is the best platform to migrate from Magento Go
As far as I know cart2cart has announced a possibility to migrate from magento go to magento community automatically. http://www.shopping-cart-migration.com/shopping-cart-migration-options/5202-magentogo-to-magento-migration
I agree with the other commenters. If you're going to go it alone, and don't know languages like PHP, Magento won't be easy. It's open source, but it's robust and highly flexible and extensible. It's not always the best solution for a startup.
​
Is there something specific that made you feel that Magento was the best fit for you? (ie. Are there any features or functionality that you felt you'd get out of Magento but perhaps not a solution like Bigcommerce.com?)
​
For many merchants, Magento is absolutely a better fit, but it's not a one-size-fits-all. Alternatively, you might consider using Zoey.com which is built on Magento, but is SaaS with a lot less backend setup and maintenance... However, Zoey starts at a higher price point than some SaaS solutions.
Their business model is a paid professional version and after some years, they put the latest features in the Open Source version which is called "((OTRS)) Community Edition". If got compare the version numbers, you'll notice that the paid version is OTRS 8 while the Community Edition is OTRS 6. You can find it here https://community.otrs.com/. For your use case, as mentioned, have a look at the customer authentication backend database (will require a bit of coding with Magento API) , dynamic fields, process tickets and webhooks. I'm sure you can nicely integrate OTRS with Magento and you'll get a powerful toolchain.
>https://magento.com/tech-resources/download
I think it's best to stick to the real Magento which is 1.9.X.X (or Magento LTS, the real opensource e-commerce). Too many breaking changes in M2, like M2.1 to M2.3 cannot be upgraded in one command. There are many modules that are not compatible anymore and needs to be upgraded as well. O__O
Now upgrading to M2.4 from 2.3.5 is not as easy as one click. You need to configure ES and refactor your modules to support PHP7.4.
As a relatively active Mod, I'm not particularly happy about this rule. Magento is 100% my career since 2008. It has its shortcomings and this is not Magento.com, it's not Stackexchange and I want 100% to be able to talk openly about Magento's shortcomings both in the stack itself and the way the company manages it.
So on the positive side, the questionaire is generally not too bad and the requirements are basically things you should already be doing in the first place. Magento has a list of 12 things you should be doing, if you're doing those 12 things the questionaire is relatively painless https://magento.com/pci-compliance.
I'm guessing you're filling out SAQ-A? https://www.pcisecuritystandards.org/documents/PCI-DSS-v3_2_1-SAQ-A.pdf?agreement=true&time=1579115385215
After you make sure you do the 12 things Magento recommends: Look at each of those requirements and try to work with your developer to write a 1 paragraph explanation of how you comply, if you can't do that you're probably not compliant. For example Requirement 8: You have site admins, who are they? What are their login IDs, are they all separate?
The flash buttons were replaced in SUPEE-8788, you're just running an older version. Best solutions is to update your installation with the latest patches. More discussion about it here
As with any piece of software, It's always better to stay up to date with the latest version. Having said that, if you are on an earlier version, you can always set up a Magento security scan to check the integrity of your site before switching.
​
Setting up the Magento Security scanner is a simple process. Go to the Magento security centre After that, simply login to your account and follow the steps from there.
​
The scan will tell you if there are any vulnerabilities that need to be addressed. If it turns out you do have any issues on your site, these should be raised with your development team. If you don't have a developer, I'd recommend seeking one out. You can find out the best way to find a Magento developer in this article here.
​
Hope that helps.
Although it isn't really formatted as a "roadmap" per se, the Product Management Team held a webinar on October 31 for developers where they covered the new features that are currently included in the 2.3 beta. The landing page for that webinar (warning, registration required) gives you a decent overview of what's included in the nearly one hour webinar, but if you want to go straight to the video, you can also watch it directly via the new DevLogs channel on YouTube.
I have a similar need and had to have some customization done. Unfortunately the custom code was unstable and virtually none of it was compatible with Magento's upgrades after 2.1.7. I needed the newer version of M2 for the 1000's of fixes in 2.2 so I'm 1 year off schedule for repairs to all customizations.
​
My advice would be to use caution with hiring a dev and keep it as simple as possible so as not to run into issues when upgrading later.
​
Magento has also launched a service that could help answer your question. I wish this was around a year ago when I was having problems with my dev at the time - perhaps it could have saved me a lot of time and money! https://magento.com/services
​
Hello, I'm currently studying for this exam and I've taken your practice exam and have been reading through your study guide. I have found at least two questions where the practice test 'correct' answers contradict your own study guide and magento.com
I'm sure more technical readers here can help. I'll point you in the right direction. Look for SUPEE-8967
From Magento.com:
This patch contains update for Magento to correctly recognize update BIN range of card numbers from Mastercard. It is applicable only to Magento versions prior to CE 1.9.3.0, and is already included in versions CE 1.9.3.0 and newer. For versions older than Magento CE 1.9.0.0, a previous patch for Discover changes (SUPEE-2725) need to be applied first.
Oops, I linked to the wrong place. I was trying to link to Magento DevBox Beta that was mentioned in the admin notifications in january. But thank you anyway.
I'm going to throw out look for a Magento partner. While you can find a freelancer who is worth their stuff....a much better chance you do not.
You can start here: https://magento.com/find-a-partner
Depending on your size Magento would also work with you to find a partner that fits what you are looking for.
If you are hosted with someone, you can also ask them, they have trusted partners they can recommend to you as well.
Can highly recommend the Magento U videos - they do cost, but we've found the best way to get existing PHP developers up to speed on Magento: https://magento.com/training/overview
They have videos for Magento 1 and 2.
Totally agree with jesse_dev - can't imagine hiring a developer who only knows Magento 2, so a bit of Magento 1 development experience is likely to be essential. Certainly a lot of the terminology and processes in Magento 1 are transferable to Magento 2.
@HalfPintBob
Not sure if you saw this - Here's a statement from Magento on Guruincsite. They say it's a new exploit of the shoplift vulnerability.
You should setup git on the server so that it is easier for you to push your changes to your remote servers - QA/Staging/Production -whatever.
Git has a guide on how to set up a remote server: https://git-scm.com/book/en/v2/Git-on-the-Server-Getting-Git-on-a-Server
Depending on your needs and the depth of automation required in the deployment process you have loads of options to push your code changes from the local environment to the production environment- using hudson, git hooks or switch branches manually on the remote server.
The simplest approach would be to set up git on the remote server,add all the files to the repository and then clone the said remote repository onto your local server. Whenever you want to push changes to the remote production server you could push the local changes to the master branch. Git won't let you push to the remote master branch if the remote git server is checked out into master. Before pushing to master, you could switch to another branch on production. Push from local to master and subsequently switch to master on remote server. The aforementioned would be based on the policy that only the master branch is checked into on the remote production server. This is the simplest basic way to start, you could refine your deployment process as your needs arise later.
There might be a learning curve involved so I'd say just start small and basic and play around it. You will be amazed at how convenient development becomes with a git workflow in place. There have been times in the past when I'd have turned down clients just because they has FTP set up and I find that a PITA, not worth a developer's time no matter what. All the best.
if you find the learning curve too much don't give up, maybe hire someone to take you through the detailed set up and teach you basic stuff around the git workflow. It is certainly not something you going to get good at in 4-5 hours but you could well get upto speed in a few days.
I installed the module in a test environment, and I do see the fee in the admin: https://snipboard.io/tNe5iL.jpg
So I'm not sure what's going on with your store. Do you have a lot of overrides (or modified core files) for the admin design package? Edit: or perhaps another extension that conflicts? It would have to be a pretty badly coded extension to do that I think.
After install fresh without sample data magento 2.3.4 file getting the same error?
select * from catalog_product_index_eav_temp LIMIT 0, 1000 Error Code: 1146. Table 'magento.catalog_product_index_eav_temp' doesn't exist 0.00055 sec
screenshot : https://snipboard.io/2KUIQr.jpg
I am searched regard this issue but not getting proper guidance.
Note : I am getting the above error when i run reindex.
1) Is modrewrite enabled?
yes, https://snipboard.io/TgLOrj.jpg
2) Is your apache2 vhost set up with allowoverride all?
<VirtualHost *:80> ServerName localhost ServerAlias localhost DocumentRoot "${INSTALL_DIR}/www" <Directory "${INSTALL_DIR}/www/"> Options +Indexes +Includes +FollowSymLinks +MultiViews AllowOverride All #Require local Require all granted </Directory> </VirtualHost>
3) Have you checked the admin frontname in env is what your using?
'backend' => [ 'frontName' => 'admin_1ryr5t' ],
4) Have you come straight here without googling to look at the hundreds of questions that already exist with the answers?
No
Price template : https://snipboard.io/l9Jot6.jpgand also check with fresh default magento file, still getting same error. How can i solve this error? I tried almost 5 days, pls help me to get from this unexpected error?
very good advice, that's what helped me the most along with a few Udemy.com courses from Brad Traversky and Maximilian Schwarzmüller on JavaScript and then of course Alan Storm's (now a bit outdated but still helpful) blog.
Hi I saw https://statically.io/ and it seems to work fast and is free. I also looked at Thumbor if it would be worth it to install our own Thumbor. Imgix sewms to have monrhly fee.
Would you know if Magento 2.4 remote storage can accept S3 compatible storage solutions like DigitalOcean Spaces? I couldnt find any article to make Magento 2.4 connect to an s3 compatible storage
What the PHP Handler. I remember having issues like this, and it came down to apache having its own timeout directive, which would cause the process to terminate. (http://httpd.apache.org/docs/2.2/mod/core.html#timeout)
Basically, having htaccess files enabled means the server will need to check each directory for the existence of the file, and it rereads it frequently (could be with every request -- never dug in to that). The Apache manual has a thorough explanation, if you're interested in reading more about it.
Unfortunately, it sounds like you're on shared hosting, so you won't be able to move the htaccess stuff into your web server configs, nor will you be able to turn htaccess files off.
I'm also not sure if this is the cause of the problem you're experiencing.
KeyCDN is a great CDN. We've saved money with KeyCDN compared to other CDNs and also the feature set is very good. I've never had any issues with the CDN and I can recommend it.
Well crud. Do you code at all? I have a solution for the not patching thing but I am hesitant to recommend if you don't code. I'm not sure what Magento package you have with Nexcess but they will create a developer/sandbox instance for you if you can't create a local version yourself. If you can get either running, you can go here https://www.magentocommerce.com/download under the release archive and download a copy of the release you have and then use this tool http://www.scootersoftware.com/download.php to compare them and find the core file that has been modified and hopefully see why it was. You could then restore the file and apply the patches or upgrade yourself to the latest 1.9.2.2. Test and make sure your site still works as expected and if so, patch or upgrade the live version.
Coming back to this post, Any fast Magento store in my experience leverage Varnish (Rather than FPC and other attempts to replicate Varnish inside Magento).
Once you have a working caching layer infront of your servers, then it would be appropriate to look at whether you should run on dedicated or shared.
Normally the question doesnt come back to dedicated / shared, Its how can i get Varnish to cache more.
Looking to the future, Its all about Varnish - Magento 2 has thrown away all other page caches and works with Varnish out of the box: https://www.section.io/magento-2-varnish-cache/
/u/d_rbn is correct, these are magic methods
The real problem is though, the Magento developers were pretty inconstant on PHPDoc'ing the magic methods available. If you really want to get rid of this error, you would go into the various classes and add some PHPDoc notation to the class definition comment defining those functions.
Also they sometimes PHPDoc'd functions that they later implemented, causing more issues.
For example, the Mage_Catalog_Model_Product class (app/code/core/Mage/Catalog/Model/Product.php) should go from:
/** * Catalog product model * * @method Mage_Catalog_Model_Resource_Product getResource() * @method Mage_Catalog_Model_Resource_Product _getResource() *
to something more like
/** * Catalog product model * * @method Mage_Catalog_Model_Resource_Product getResource() * @method int getEntityTypeId() * @method Mage_Catalog_Model_Product setEntityTypeId(int $value) * @method int getAttributeSetId() * @method Mage_Catalog_Model_Product setAttributeSetId(int $value) * @method string getDescription() * @method Mage_Catalog_Model_Product setDescription(string $value) * @method Mage_Catalog_Model_Product setTypeId(string $value) * @method Mage_Catalog_Model_Product setPrice(float $value)
Standard documentation notation for any magic attribute you're looking to retrieve is:
@method {varType} get{AttributeName}() @method {currentClass} set{AttributeName}({varType} $value)
http://www.phpdoc.org/docs/latest/getting-started/your-first-set-of-documentation.html is a good starting place to learn PHPDoc if you don't know it.
seems like after further research, a possible way is to
- run bin/magento setup:upgrade locally
- copy the extension files to production
- run bin/magento setup:upgrade on production
also ran across a cool tool at
there's not a recipe for magento2 yet, so I will see if I can come up with one. If anyone else has one, that would be helpful.
Try running this query:
update sales_flat_order set trigger_recollect = 1.
This would force all the quotes to be recalculated whenever they are loaded. see : Mage_Sales_Model_Quote::_afterLoad() method.
I think you see different prices because products have already been added to the cart and magento has no way of knowing that the prices have been changed.
You could also write a shell script that loads all the skus during emulation of the admin store and saves them. This would have the same effect that saving products manually from the admin has.
You can add the code here to a file in the shell folder and run it: http://justpaste.it/lz5v
- Enter weights into the weight field.
- Get silver price from API
- A daily cron that loops through the full product collection, and saves new price based on the data from your feed and a little extra calculation. Very roughly it might look something like this.
I'm just a caveman, but isn't this a textbook case for Configurable Products?
As in, you set up Simple Products for the various combos your shirts come in (one for each shirt-color-size) to create the Configurable Product. Since there are no 4XL tanks, that size option would not display for tanks.
I looked into Porto's test site, it looks like they use a modified Bootstrap that removes those classes, for whatever reason. I tested on their demo site and it looks like it's using Bootstrap 3 classes for responsive display. Try these out instead:
Roughly, you need to:
Export a DataFlow Profile (.csv) from Magento. This will give you the correct column header names.
Reasearch and install Magmi.
Using OpenOffice, open the .csv from DataFlow. Make any modifications needed (add or remove columns).
Use Magmi to import the .csv into Magento.
???
Profit!