-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Manage Banner" section pointing to BannerSlider #56
Comments
Yes this was the issue, also fixes this: |
List of files i replaced "BannerSlider" to "Bannerslider" (cause namespaces and class names are case sensitive), after replacements all works like a charm. Tested on version 2.1.1 Controller/Adminhtml/AbstractAction.php |
@friizu If i have my vendor_module name as Magestore_ Bannerslider, why do i change Bannerslider to BannerSlider ? The namespace depends on vendor_module name given on directory, right ? |
You are right, don't! I replaced "BannerSlider" to "Bannerslider" not other way around. |
@friizu if i have vendor_module name as Magestore_Bannerslider and namespaces as Bannerslider, the error is same, how can i solve the problem ?? |
@sgrspkt - as on first post this thread and my previous post, you need to check all files I listed, for example:
You see path BannerSlider (what needs to be Bannerslider) and so on ... so you need to make replace to all those files to make this module work fluent. ps. if u wanna make mass replace on those files be sure that you'r replace is case sensitive! |
@friizu, Thank you. I solved the problem of manage banner after replacing 'BannerSlider' with 'Bannerslider'. |
@sgrspkt here #66 (comment) you can find our implementation |
@friizu your solution worked for me. Thanks |
After a fresh install of the 1.7 version, I was able to create a new slider, but when a hit the "Manage Banner" I'm getting some errors. I've created a Bannerslider folder, but some sections of the code are referencing BannerSlider. I've just replaced all those entries with Bannerslider, and now works perfectly.
The text was updated successfully, but these errors were encountered: