I have installed Opencart 2.0.3.1.
vqmod 2.5.1.5 for Opencart,
vqmod manager 3.0,
and ProductQuestionsAndAnswers_v1.8.2_oc2.0.x.x
These have all been uploaded manually via ftp, i've followed the simple instructions for vqmod's installation to rewrite part of the index.php and admin/index.php which seems to have created all of the required cache files.
The module is installed, enabled and visible in the modules section and in the vqmod manager, however when I try adding the module to the theme layout there is no option for this module.
Everything appears to be working fine other than for not being able to insert the module into a layout.
Not all modules for Opencart have that option to add it in a layout.A big portion of the modules in opencart are made by students or people that are learning to code most of the free modules don't even have that option. Now that we have this out of the way.
Other solutions to this problem.
If you are using a custom /admin panel lets say your admin is called bestbanana
You need to open the VqMOD xml file that is located in the VQmod/xml folder
and change all the values that contain admin to bestbanana
Or if you are using a custom theme that has different structure than the default opencart one,than you need to modify it a little bit more.
Since VqMOD works as a search engine it searches/replaces adds and so forth bu it searches by exact words. e.g peaces of code.
but without posting any code or something similar there is nothing much that anyone can help you with.
Hope that this will help you
Related
I'm new in WordPress
I misunderstand one thing about the theme use in WordPress
For example, I wanna create the as same website as this I purchased this template.
But when I installed the theme in WordPress it shows me the default Index.php file with little info, used my purchased theme
And when I purchased the theme there exist all src files of the above website.
How I can use my purchased src files of website that will work all function for ex: logins with db?
Thanks in advance!!!!
After you purchased the theme, you probably have just installed the theme and haven't created any pages or tweaked any settings. So if you want to get the same look as that of the preview website, you probably have to check whether the developer has provided any dummy data for importing.
Most of the themes listed in ThemeForest would have the option to import dummy data, so that customers would be able to install some pre-made posts, pages, config, etc. This might be there inside the custom settings page(as a single button to download the content) of the theme, or maybe they have provided it in separate XML files for you to import. If the files you have downloaded doesn't have it, make sure you downloaded All files & documentation. Here's a sample screenshot:
My guess is that you might have only downloaded using the Installable WordPress file only option.
If you are still unable to get the dummy data, probably you have to ping the support of that theme asking them to provide the dummy data.
I recently had a task dumped on me, all I need to do is add a link header to a template in joomla. I'm able to do this directly inside the default.php in
/modules/mod_articles_category/tmpl/default.php
but of course it shows up in any module that uses that template, which isn't acceptable.
I havn't touched joomla before yesterday and I'm suprised at how painful this has become!
I've been following tutorials, creating an override template in
templates/template_name/html/mod_articles_category/default.php
but I dont see any option to utilize this override template in the module options of the admin console.
I also tried creating a duplicate of the module itself with the link header simply added into the default.php file but don't have any option to have this module installed since there is no module manager extension, just barebones joomla 3. What I'd like to do is use the override template, since it seems like the simplest solution.
What am i doing wrong that I cant see any effect from my override template?
Rename the file templates/template_name/html/mod_articles_category/default.php to something custom like templates/template_name/html/mod_articles_category/linkInHeader.php then save it.
Go to your module manager and open that module. GO to Advanced tab & select linkInHeader in Alternative Layout dropdown. This should do the tricks.
I am developing mobile application for existing magento website and the mobile application has its own web admin and web admin developed in core php (not in magento). Can we put the core php web admin code to magento /app/code/local/ folder ? and is it work with magento ?
Please help me on this.
We can consider Magento as an application that is constituted by modules. Each of this module does different functionalities, but still they are independent to each other. This property makes Magento highly extendable and powerful.
By default, Magento comes with lot of such individual modules. These modules are located inside app/code/core. Note that, this folder only holds Model and Controller logic parts. View logics are separated from this and it normally lies in app/design and skin folders.
If you need to extend Magento core functionality or if you need to add any new functionality, you have two options available.
Use an extension
Develop your own custom modules
For extension/pluggin, Magento uses app/code/community directory. This way core modules are seperated from extensions and it gives us lot of flexibility.
When you use your own modules to add any functionality, you probably need to add your module in app/code/local. This way, custom modules are seperated from both core and extensions.
When Magento looks for a module, it will first check that module in local directory. If it is not there, then it will check in community directory. If it is not there, again it will check in core directory. Finally it will check it in lib directory. This callback mechanism is the core concept that you need to understand , before start to develop your own extensions.
It is not necessary to put your custom module in app/code/local directory. You can put it in community or in core directory. This is because, the callback mechanism can pick up your module, irrespective of these three locations. However as I said earlier, three of this directories has its own purpose. So better use them properly as it demands.
Hope that makes lot of sense
From Magento Wiki,
Every custom module will be created in the directory:
/app/code/local
And this is the directory structure that you use to create one:
/app/code/local/<Namespace>/<Module>/
That way, we can have multiple modules under a single namespace.
Naresh, /app/code/local/ is used to put your custom developed plugin/extension for magento. it's main aim to have custom developed code and core code separate.
If in future you upgrade the version of magento than it overwrite/delete the code written in /app/code/core/ but leave the code as it is in /app/code/local/ and it's place where you can override the core block/helper/model as well.
you can't copy your code directly in to core, you have to create module/plugin to club your existing code with magento.
How should I be doing the following
- adding new form fields to the product edit page
- adding a new menu item to the admin console main menu
Are there any hooks that can be called from my extension?
Or
Should I be editing the core files itself to add this functionality?
OpenCart is not a Wordpress and has no hooks You could use to Your purpose, nor it has no events nor event listeners that could be used as well.
When implementing some functionality for OpenCart for long time we only had the possibility to edit the core files directly which led to work lost when we updated to newer version, also installing plugins/extensions modifying core files was possible only in way open file A, go to line XYZ and place this code there. Then go to file B ....
In past few years we have a possibility to use vQmod which was improved rapidly and using this You are possible to inject Your new code into existing core files and remove or modify some of the source code in the core files with the certainty Your changes are not lost after the update to a newer version. Of course, Your extension may stop working but it is a lot easier just to modify the changes in XML file then to re-implement all the lost work again (and again).
Similar to vQmod there is also some Override Engine that should also help You to implement extensions apart from OC's core files but I haven't tried it yet.
Note: I have already posted this question on [SE's drupal] but didnt got any positive response there so i am posting same question here again.
I want to organize non-core(modules that are not bundled with core) modules in Drupal 7. This is my proposed structure:
Contributed modules - downloaded modules that are untouched
Custom modules - downloaded modules that are modified to suit the requirement
local modules - self-developed modules
I GUESS, the best approach for this is to make three folders within sites/all/modules like below:
sites/all/modules/contrib
sites/all/modules/custom
sites/all/modules/local
Now, there are two ways to install a module:
Manually
From the admin panel
While installing the new module manually, everything is fine. I can just go to the directory and place the module there. But how to install a newly downloaded module in `sites/all/modules/contrib from admin-panel. Moreover, is there any better approach for organizing non-core modules?
Finally after banging head on google for hours, asking question on SO and SE's drupal and communicating with other users via comments, I cracked it...
Well, the directory structure is still debatable but satisfactory for me. But the answer to the most imp question is "DRUSH".
Refer this and this node from Drupal. Collectively, it has everything needed to answer my entire question.
I would also like to point you to this answer which has provided the first and most-imp hint to me.