Merged
Conversation
refs #2386
Added additional details regarding Apache mod_proxy_fcgi auth/login issues. Cleaned up and formatted the README using GitHub Markdown.
Formatted README; Apache mod_proxy_fcgi info
Fix Polish accented leters transliteration in Slugger
…gurable and simple) in the "options_container"
Bugfix in configurable item processor plugin
…sibly image processor is waiting for images fields before gallery fields. Patch is to make sure they are always in the right order
First image can be excluded during magmi re-import with no reason.
Add Attribute Deleter Plugin.
Added timeout for big files on remote download mode
The current recommend and only way of using magmi to create a
category root for each store (not store view) and then through mange
stores assign it there. That means you are forced to create a store for
each language, however the recommended way to make translations of a store is to create a store view for each language.
You cannot set the category root on store view level. So the idea a root
per language doesn't work in this case.
This PR address that by implementing select option style translations
with this syntax:
```
catname::[defaultname] or you could say
danish::[english]
```
Everything works as before in terms of hierarchies:
```
mænd::[men]/sko::[shoes];;kvinder::[women]/sko::[shoes]
```
Basically it just swaps the default name into the first position and
stores the translate name as an option like `is_anchor` and `is_active`
and so on.
You can combine this with the just mentioned options like expected:
```
mænd::1::1::0::[men]
```
and even with position (something that wouldn't have worked before):
```
mænd::1::1::0::[men]::5
```
(Note: due to existing impl. position has to be the last value and you
have to include all three or none of the others)
If you switch between store views in the admin you'll see that it is the
same category tree you are working on. So this is the right way to do
translations.
Fixes #462
Implemented category translations ala select option translations.
…is will allow plugins to use it.
Check for category position before preparing for database insertion
…n ids instead of the fulltext
Fixes #498, set group prices on website scope
Added Turkish leters
Added Turkish leters
Replaced short array syntax
…s-in-magento-1-9-3 #494 - When attribute is multiselect
Update README.md
Added gitter chat
mutiselect_sep => multiselect_sep
Fix type in multiselect_sep
Fix Advanced Utilities for Group Price
fixed ajax_gettime.php
fixed ajax_gettime.php
Fix category product position when base category tree is setted on plugin configuration o some category not have ::x::x::x If Base category or some category not have ::x::x::x set array $catpos is not in sync with $catids array (see line 375) and category position not working correctly.
Fix category product position
if ($ovalue !== false && $ovalue != null) returns wrong result in php 5.6.30 and sets $ovalue as false
null equality issue
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.