Is there any tutorial available for how do i add custom fields on front end check out step like PO number,Job name , customer comments etc as well as in admin->create->order.
My usual motto is to find (and buy if needed) a module that already has the functionality you seek. Especially when the life of this project involves version upgrades because then you can seek a pre-packaged solution from the provider.
I regret every bit of custom code I have added to our Magento install. Because now I've got to maintain the site to just keep working in addition to figuring out my hacks. Time to devote more time to replacing hacks with off-the-shelf extensions, which would have been much faster in the first place.
I know this attitude goes somewhat against the stack overflow thinking of I can do anything, but really, Magento's job is to enable someone to do less work.
Two years later, an update: after the gentle poke of a downvote (probably for appearing to shrug off the question), I am back to revisit and share some of what I've learned. The programming aspect of additional fields is the concept of persistence of the data.
If you're ok with the custom fields only appearing in the transactional emails following the order, then the task is as "simple" as adding the fields to the form somewhere and then updating the controller to to catch and insert the post data into the email. You can use a custom variable in the back end to readily expose this to the email templates. And a Magento SE on programatically creating a custom variable.
Getting persistence into the back end requires adding database fields via an installer in your module. The iCoreThink blog lays out the steps clearly and explains why, how to confirm your work, and then provides real-world implementation, like displaying to the customer in their account. The "other blog" mentioned below has a great example of this, though his example is specifically related to billing and shipping.
Resources from my upvotes and bookmarks:
» This iCoreThink blog post is my favorite reference so far and what I'm following now.
» I was using Templates Master's FireCheckout which includes their own checkoutfields module, but I've abandoned their single view checkout for the flow of Magento's one page checkout. I'm now trying to adapt their checkout fields (and use their controller) into my template for checkout.
» I thought for sure Alan Storm wrote an article about Checkout custom fields, but I don't see one.
» This Magento SE lists a couple blogs and a paid extension. The excellence blog is ok, but his style is too rote for me and I don't learn anything. The other blog discusses the procedure for building your module and installing the database fields.
» The unexpected-IT blog demonstrates and informal hack to add the code to core files (but sadly doesn't show how to override those files by copying them to app/code/local) and the steps to manually perform to get the column and fields added in the database. Apparently is perfect for 1.4 and below, but comments seem to explain what to do for 1.5 and up.
This last hack-ish change is my personal favorite as it seamlessly adds the extra bits into existing Magento admin pages and "feels like" less work. Caveats: I wouldn't do this without using version control and it will absolutely break if any core code changes happen between version upgrades.
Related
I have created an ecommerce store, and I'm using PayPal "Add to Cart" Buttons with what they call 'hosted' buttons (PayPal stores the buttons on their servers) for each of my products.
For reference on how they work (and why I use them):
You create a button(product) inside your PayPal Dashboard and you define the quantity available (most of them are 1 in my case)
You copy the HTML code into your website (or just copy the link)
The user buys the product (and the quantity falls -1)
The reason I use this setup is because my website is static, and PayPal provides the Quanity (SKU) Management - so no one can buy a product that no longer exists - even if he can access the button/link.
My Problem
The PayPal GUI dashboard for creating buttons is very time-consuming, I would like to have the ability to edit/create etc. buttons in bulk.
I had search and search for a solution online but have found nothing.
Possible Solution
The only thing I've recently gave some thought was the PayPal Button Manager API and the Ruby SDK in particular, but even if I've studied programming and I'm really eager to keep learning more, I don't know yet what to do in order to make the API calls.
I can't understand from their documentation and I have found zero tutorials online for such a thing.
Failed Solution
As I was familiar with WordPress I tried installing a plugin called PayPal Button Manager but it hasn't the ability to edit in bulk, which is what I'm trying to do.
All in all, I want to:
Create, Edit, Delete, Update in bulk PayPal Hosted Add to Cart Buttons
If using the Ruby API, I would much prefer doing so in a local environment
I'm using Jekyll for my static site, so I'm having Ruby installed and have read multiple times that it's an 'easy' to learn language. But if you can think of something else, I'm open.
If you have Wordpress, then you have a local database, and might end up much happier with a solution that stores quantities locally in that database, such as the WooCommerce plugin, with the following additional plugin for payment: https://woocommerce.com/woocommerce-and-paypal/
Your proposed solution of using PayPal Standard Buttons with the legacy PayPal Button Manager API .. is extremely unconventional in contrast, and would be considered a "terrible, horrible, no good, very bad" hack by most.
I am new to this software. I was just wondering how to create/edit/check header, side, and footer link. What I have noticed so far from numerous searches is that it requires some type of actual manual programming. And also if it is not a template, I would have to add it through Static Blocks or Edit it through a .phtml/.php/.xml file which I have no idea to do. Assume I have the latest software. Any help is appreciated.
You can create a shop in english without manual coding at all. But you will get the result you asked for. A hard application without any customisations which probably will not be valid IRS-wise(for example, the invoices in Greece have to contain very specific things. If not they are not valid and you get fined.). The header and the footer are customised by Static Blocks from the backend of Magento without trouble. You will have to search for a documentation of your template ofcourse. There are so many information and we cannot give it to you with just one post. You will have to study and ask the right questions!
I added 2 tables, for now, maybe will need more and I'm looking on how to add an administration page on the backend side. I found this SO question Magento: Custom Module: How to Manage with Multiple tables that is extactly whay I need. The answer given is just, in my own words, that's too dificult to achieve and too long to explain in SO.
So, anyone willing to share some link, tutorial or DIY step by step explanation? I've already my models working and configured, thanks to #AlanStorm tutorials. I'm doing CRUD operations from within my code but I need to do it from backend on a window for administration purposes.
I thought this Magento Custom CRUD Application Tutorial would help me but it involves using magento ModuleCreator plugin and is not working for me on magento 1.7.0.2. Also I already have my own module fully configured so lot of what module creator adds is not needed.
Found this sample/tutorial/code but I'm having hard time following it, lot of obscure points and not sure what I'm doing, even if it is correct.
You could definitely benefit from some adminhtml grids, there are no shortage of tutorials if you look for them. I wrote my own which I now shamelessly plug here.
I have some sites that I implemented using Drupal. However as cool as Drupal is I've never been satisfied with coding in it mostly because it's in PHP and I've wanted to work with python. I've flirted with Django but I just recently discovered web2py and it's definitely caught my eye. Seems like it may be a sweet spot between Drupal and Django. Although django-cms is also on my radar.
So now I'm wondering how to re-implement my sites with web2py. Specifically suppose I have a site about DVD players. So in Drupal I'd have a CCK type DVD player, with various attributes. I guess this would correspond to a web2py model. How would I implement something like Drupal's taxonomy which is like a tagging system in web2py? Is there a module/plugin/appliance for that? Or am I manually creating the model schema to handle tagging?
Secondly, how would you handle something like comments and/or reviews on posts? Again, is there a pre-built plugin for this or do I have roll my own?
For tagging, I don't think web2py has anything quite like the Drupal Taxonomy module, but there are some options. First, you could create your own many-to-many model to assign tags to items. Another simpler option is to use web2py's list:reference field type to de-normalize the many-to-many relationship (the end of that section in the book includes a tagging example).
For existing tagging solutions, you can also check out web2py's plugin_wiki, which includes a tag widget. You can get it from the download page, or pull the source code directly. Another option is Powerpack, which includes the Instant Press CMS, which includes tagging and categories functionality.
Also, both plugin_wiki and Powerpack include comment plugins.
Finally, you'll generally get more and quicker responses from knowledgeable web2py users on the web2py mailing list.
we are using magento with onestepcheckout module in our shopping system. But when the payment process fails and when we get an error about payment, not all but some translations fails on the checkout page.
Has anybody face this problem before. I will be very happy if there is an solution.
P.S. I can solve the situation by hard-coding the translations. But I dont want to use this method.
Thank you
When a module developer creates a module, it's up to them to make sure that each and every phrase that could be translated is marked for translation. In Magento this means
Strings in template files are passed through the ->__ method
Labels, parameters, and other strings in XML fiels are marked with translate attribute
As an individual developer, if you're not developing applications/modules intended for translation it's easy to fall into the habit of not doing the above. Also, the areas of Magento's XML configuration system that can (vs. can't) be translated aren't well documented. It's easy to miss a string or two, and localization (along with everything else) is almost never tested.
All of which is a long way of saying, contact your vendor and file a bug. If you want to play capitalism, since you've already hard-coded the translations, fix the core problem yourself and offer to sell the solution back to the onepage people.