I'm working with a learning management system called ILIAS; trying to develop a plugin for the PersonalDesktopHook [pdhk] plugin slot.
Sadly I'm stuck with deploying the simplest plugin:
Created a directory for my plugin:
ilias/Customizing/global/plugins/Services/PersonalDesktop/PluginName
Created a plugin.php file as described in the documentation (with matching id, etc.).
Created a classes/class.ilPluginNamePlugin.php file containing a ilPluginNamePlugin extending the abstract ilPersonalDesktopHookPlugin class located in
ilias/Services/PersonalDesktop/classes/class.ilPersonalDesktopHookPlugin.php
Still my plugin isn't showing up in the Services/PersonalDesktop component menu (Administration).
Did I miss something or is the plugin development documentation out of date?
(I followed the ILIAS development guide's "Implementing Plugins" section.)
This answer is late, but this seems to be a common issue in ilias plugin development. The following things should be checked:
Is the path really correct (including case of the file/folders name). In this case it isn't, it should be: ./Customizing/global/plugins/Services/PersonalDesktop/PersonalDesktopHook/PluginName . If you are unsure consult: https://www.ilias.de/docu/goto_docu_pg_27031_42.html or the xml of the corresponding service/module, in this case: ./Services/PersonalDesktop/service.xml
Check that you have a plugin.php file with the correct $id set (in this case: pdsk).
Check that your webserver has read permissions for you plugin to be listed in the administration.
Related
I am trying to override the template file for the environment panel in the CakePHP 3.0 DebugKit. The file is located at
app/vendor/cakephp/debug_kit/src/Template/Element/environment_panel.ctp
According to the docs, placing my own file at
app/src/Template/Plugin/cakephp/debug_kit/Element/environment_panel.ctp
should automagically display my template instead of the plugin's, however, my file is being ignored. I've tried leaving out the cakephp directory, and using camel case for the vendor/plugin names. What am I doing wrong?
After two more hours of experimentation I found the correct path:
app/src/Template/Plugin/DebugKit/Element/environment_panel.ctp
To clarify the confusion I had: the debug kit is not considered a composer/vendor-type plugin mentioned in the docs I linked in the question, so it doesn't need the ../cakephp/.. intermediate directory.
Additionally, the directory needed to be CamelCased instead of copied verbatim from the vendor directories.
ALSO: in apparent conflict with the Element docs, you CAN override a plugin element without setting the ['plugin' => false] option.
I have been cracking my head about this for two days on. I inherited some magento 1.9 Multi vendor website and just need to bolden some text on the customer create account field. I have searched every where in my template directory Customer/form/register.phtml and Persitent/form/register.phtml yet I am not successfully able to identify the line that prints
'wants to become a vendor?'
Here is a link to the form please.
http://store.min-trade.com/index.php/customer/account/create/
Could someone point me in the right direction. I pretty much understand the project structure of Magento I do believe. Please help!
Are you sure you are looking in the correct template folder?
You are using the rwd/default template, so have a look here;
app/design/frontend/rwd/default/template/persistent/customer/form/register.phtml
If there isn't a file called register.phtml in that location, then Magento will fall back to the base folder, so try;
app/design/frontend/base/default/template/persistent/customer/form/register.phtml
If you still cannot find the text, it could be a custom login form using another template. Login to your server with ssh/putty and run this command;
grep -nr 'Wants to become a Vendor?' /path/to/magento/*
Just make sure you set the correct path.
You can easily check by enabling path hints from magento admin.
If you dont know how to enable file path hint then refer this link enter link description here
second thing that if you have installed any vendor extension then register form will be displayed from that module.
You can also install this path hint module for check file.
I am currently using CI 2.1 and Netbeans 7.0 as my inveiglement IDE. I would like to create some simple unit testing using SimpleTest. In particular the methodology used by Eric Barnes and his code found at Git Hub CodeIgniter-SimpleTest. (https://github.com/ericbarnes/codeigniter-simpletest)
I have created a new CI application using Netbeans 7.0 and connected to my database (which contains 1 table called schools with the typical schema schoolid, schoolname, schooladdress etc.). I have created a controller (simpleapp), which loads a model called schools_model. The schools_model gets all the schools using a method called getAll(). Another method called getSchoolName(id), accepts a school ID and returns the school name.
The controller then loads a view called schools_view to display all the schools. Pretty simple stuff…....... and it works flawlessly, displaying all the schools when I point my browser to
http://localhost/SimpleTest/simpleapp/getAllSchools
(I am also using a .htaccess file, hence no index.php)
My question is this….......
How do I get SimpleTest to work using the Git hub code supplied by Eric?
I have followed Eric’s set-up advise, but don’t know what URL to point to to create the screen dumps he provides. I have maintained the directory structure Eric suggests but haven’t had any success. Eric suggest to point the browser to yoursite.com/unit_test.php, but I get a
404 page not found error for localhost/SimpleTest/unit_test.php
I assume the above error is due to the fact, like most CI applications, we need to use a controller first.
I would appreciate any direction in this area.
I have done exactly what you suggested. I have placed the unit_test.php file in the root directory and set up the test directory structure as suggested. However, when I point to localhost/SimpleTest/unit_test.php I get the 404 error.
My directory structure looks like
Source Files
-application (folder)
-system(folder)
-tests(folder from git hub with model/test_schools_model.php)
-.htaccess
-index.php
-licence.txt
-unit_test.php
Is it a .htaccess issue the reason I cannot view localhost/SimpleTest/unit_test.php?
You are correct you need to go to yoursite.com/unit_test.php or in your case localhost/SimpleTest/unit_test.php
You need to copy the unit_test.php file from github into the sites root directory and place the tests directory there too. You then put your tests in the appropriate folder under tests/
We're working on Alan Storm's tutorial: Magento Controller Dispatch and Hello World on Magento 1.5.0.0.
at the step:
Clear your config cache, and load the following URL
http://exmaple.com/helloworld/index/index
and it produces a page not found error, as follows:
Whoops, our bad...
The page you requested was not found, and we have a fine guess why.
If you typed the URL directly, please make sure the spelling is correct.
If you clicked on a link to get here, the link is outdated.
Two of us are working on this. One of us on a Linux platform, the second on Mac OS X 10.6.7. The same "page not found" error on both platforms. We both have double-checked each other's tutorial code by comparison to Alan's article. It seems that something is remiss in the tutorial code in that it would not work on two independent platforms.
What is the best way to move ahead with debugging something like this?
First check the module is active, at the very least it should appear in System > Configuration > Advanced > Disable Module's Output or use Alan's Module List.
Next, double check for typos in the controller class and pay particular attention to the case. In the config frontname should be frontName (a capital N is often overlooked).
I had the same problem , Double check your /path/to/magento/app/etc/modules/Module_Name.xml , I had the codePool set to "community" and placed my extension in "local" directory this caused the 404 issue, when I changed the codePool value to "local" everything worked
example.com (or exmaple.com as typo'd in the tutorial) is a placeholder link used in documents. You are supposed to replace it with your own hostname, i.e. if you are developing on a local webserver http://localhost/, like this: http://localhost/helloworld/index/index
Just stumbled over the same problem and found the solution to be that mod_rewrite has to be enabled on the server for the URL given in the tutorial to work. Elsewise, it will work with the following URL as well:
http://exmaple.com/index.php/helloworld/index/index
try by adding "index.php" in your url.
For example: http://example.com/index.php/helloworld/index/index
If you are done with this. Search some article to remove index.php from magento.
I am on magento 1.8 and i fixed my 404 error by doing the following. inside Magentotutorial_Helloworld.xml they tell you to put this code in "local" since i do not have a local folder i put mine into the community folder. Change the code to this and it will work. "community"
I found a guide on how to add new attributes to users, it explains that for this operation I must modify some files in the app / code / core / Mage directory (the directory that contains Magento’s modules).
But if i make some changes in that folder will this affect future upgrades?
Will an upgrade will delete my changes?
Should I limit the changes only to my modules to not have problems with updates?
You can also make a copy of the file in app/code/local/ with the same directory structure as the file has under app/code/core/. File under local will override those under core and will not be affected by upgrades.
For example:
app/code/local/Mage/Checkout/Block/Onepage/Billing.php
will override:
app/code/core/Mage/Checkout/Block/Onepage/Billing.php
and will not be overwritten by upgrades. Note that this will only work for Block and Model files.
You can also override files through custom modules with the config.xml file, although this is a bit more advanced.
Yes, changes such as these will be overwritten.
If you have such changes, try to:
keep core changes to a minimum
document any changes you make
report the issues on the Magrnto web site so that the changes can be replicated for everyone else
Controllers would work as well if you enable that Module in local space
local vs core controller