Good, is there any option to share the stock after creating the multiTienda without losing the stock that we already have ?, I have realized that if I activate this now the stock of all products is set to 0 and I can not do that because I have more than 5000 products. I have thought about modifying something of the programming to solve it, but if there is some way to do it without having to modify the programming, some module or whatever it would be milk. Otherwise, if it ever happened to you, how did you solve it? If it was done with programming, what did you do?
Beforehand
Thank you very much, and go brown ... xD
Yes, export the _PREFIX_stock_available table, and once you've done the sharing, re-import it.
Regards,
Related
I saw the possibility to change the Internationalization of Scene Builder. But I did not find somewhere suitable language packages. May somebody of you have been faced by same kind of intention? For any hints in this matter I would be grateful.
With best regards
Peter
I checked by the way the possibility to change the language of the scene-builder-menu with use of google. The result of my investigation is: It is not possible to be done by a standard kind of user. Sorry, I did not expect this result. Anyway, I learned by. Thank you very much for the time an efforts you spend to bring me onto the right way to get an answer in regard to the question i did publish in before. Thank you.
I want to create Make,model and year type work in open cart.I am new to open cart and don't know which one suite my work.Since model depends on make and similarly year depends on model value.So keeping in mind that i am unable to select which one i select for my work.Hopefully someone get my point.this type of work done in extensions but i want to do it by my own.So want to know filter will be best or attributes for this kind of work.Thanks
There are plenty of affordable options in the opencart extension store as well as codecanyon
http://www.opencart.com/index.php?route=extension/extension/info&extension_id=3621
is the one I use, love it. Developing this for yourself will be a ton of work and likely be buggy if you're asking for help here. There are many variables to consider, which is why I always advise you purchase a tested and true extension.
I'm killing myself trying to find the right solution for this problem. Here is my issue:
Selling Wires:
We will say a wire is $5.00
If you want 1 foot its $5.00
If you want 2 feet its $10.00
...
Each foot isn't a separate SKU. Its a recalculation of the total. Thats it. Really easy, but for some reason incredibly difficult in Magento.
How would I code this? Any ideas?
****UPDATE***
These are configurable products. Didn't think of that in the beginning.
One way to do this without adding additional attributes or logic is sell by the foot.
Have your SKU as wire-1-foot for example and use Magento's built-in tier pricing to customise your pricing for multiple quantities, aka multiple feet of wire.
You will probably also want to customise the block around the quantity field to make this a clearer for customers.
EDIT:
You could also consider grouped products as they behave slightly differently, e.g. http://www.webshopapps.com/blog/2010/11/tiered-pricing-on-configurable-products/
I'm using Magento ver. 1.6.1.0
I'd like to add 8lbs to each order (packing materials)
Can't find something useful in Google for "additional weight magento"
How to do this? Is there any backend option or any coding solution?
Thanks!
OK, I hard-coded that.
That's NOT the finest solution ever, but at least it works.
NOTICE: We use ONLY FedEx there, so this works ONLY for that.
In app/code/Core/Mage/Usa/Model/Shipping/Carrier/Fedex.php find something like this, line 359:
'Value' => $r->getWeight()
Here's the weight in Lbs. I've added 8 here.
Hope this will help someone.
Do it in your shipping module. This depends on what module you are using, however, you can just add to the total with a single line of code, even edit the system.xml for packing materials weight so you can adjust it. That will be vastly simpler than Ayman's solution, which I think is for a different problem.
Currently Magento has a problem with the way it handles mass actions. It returns a bit of JS that contains EVERY db id for the current collection and filter, regardless of pagination. This is to support the 'Select All' vs. 'Select All Visible' option in the grid header. This isn't such a problem when you have a smaller number of records, but if you have 850k records (orders in this case) it becomes a serious problem.
My question is, does anyone have an elegant solution to this problem?
I can think of several solutions, each with its own drawbacks, but I'm hoping someone has solved this in a simple manner that works as an add-on module. Paid or Open-Source solutions are both welcome suggestions.
Clarification:
I'm looking for an elegant/drop-in solution to the problem of 850k+ records using the grid widget in Magento. The stock Magento code makes the bone headed decision to return the id for every record that is matched by the current filter, even if they are not being displayed. This is not about offline processing of records, it's about using the grid widget for daily admin tasks.
One possible solution would be to store the results of the filtered search in a temp table and return a reference to the search result. Then you could change it from using the actual ids on a 'Select All' to using a specific callback for the action using the reference. This would preserve the current behavior.
So, to ask again, does anyone have a good solution to this already created?
I'm running heavy operations from within a shell script. I have a generic iterator (in my case products, but can be done with everything else), and I only implement a class that does the action on the product. My product_iterator shell script takes care of looping over the products, while processing only x products at once (to avoid memory leaks).
Well, the least invasive solution to the problem is to turn off the 'Select All' option for grids with large numbers of records. This is easily accomplished by extending the grid class and adding the following code:
protected function _prepareMassaction()
{
$this->getMassactionBlock()->setUseSelectAll(false);
return parent::_prepareMassaction();
}
I think that fbmc has the right general approach. Clearly, even if you did find a way to send back all 850k records, the framework would have a heart attack attempting to deal with them all. Run the logic in a shell script if this is what you need. For some jobs, you may even need to run them in batches or move down to actual SQL logic.
Unfortunately, some parts of the framework were not made to handle this kind of scale. You've found one of them.
Hope that helps!
Thanks,
Joe
Recently i have written an article about 'Adding new mass action to admin grid in Magento',
Hopefully you will like it:
http://www.blog.magepsycho.com/adding-new-mass-action-to-admin-grid-in-magento/
It describes the two way for adding Mass Action
1> Extending Grid Layouts _prepareMassaction() method
2> Using event: core_block_abstract_prepare_layout_before (more upgrade proof way)
Thanks
Regards