I am using the Zend Framework and I cannot locate in the documentation the values I can specify in the application.ini file. Does anyone have a link to where I could see them?
Thanks,
Darren
There is no exhaustive list, since you can specify arbitrary configuration values that are specific to your app.
The "built-in" stuff is mostly about configuting build-in resource plugins, so a good source of information on those might help you. The manual describes them in fair detail.
Related
I would like to retrieve some properties e.g. jcr:created using Sightly or any related syntax for the panel component in AEM adaptive forms. 1
The previous Sighlty syntaxes that I have attempted to retrieve the crx/de properties include:
${properties.jcr:created}
${pageProperties\[jcr:created\].getTime.toString}
${guidePanel.jcr:created}
${resource.jcr:created}]
I have tried the following syntaxes but unable to retrieve the value from the property and in worst cases, the component may not be rendered on screen.
I have looked up on Adobe forum sites and past stackoverflow questions that other people may have asked. I have tried the solutions and given answers but was unable to achieve the result. I would greatly appreciate for any help or sharing of applicable knowledge if you have encountered similar issues or previously attempted to solve similar problems. Thank you!
You can always create Use class in Java or Javascript to access these properties, it's cleaner and testable. Better than that, you can use Sling Models which are more readable and easier to implement, here is a good presentation about it https://www.slideshare.net/accunitysoft/understanding-sling-models-in-aem
Properties of resources are readable without any extra definitions needed.
So you might want to check what resource is handled in your component by adding this:
${resource.path}
Then you can check the returned path in CRXDE if there really is a jcr:created property available at this path - which should be the case if you are accessing a resource that has a proper sling resource type. Then this call should give a valid return value:
${resource.path} ___ created:
${properties.jcr:created.getTime.toString}
If the path is not displayed as well, then it would help if you could post
the repo path of the content resource you are processing
the sling:resourceType
the path to the component's ht(m)l file that you are using
I could not find a good example showing the correct or effective way to store the locators for easy organization/modification. Can someone point me to one?
Preferably a config file or another .js file.
Again an example will greatly help.
Thanks!
The "best practice" is to put your locators in a page object.
example: https://github.com/angular/protractor/tree/master/website/test/e2e
Docs: http://angular.github.io/protractor/#/page-objects
I'll second the use of page objects and have some additional examples on GitHub...
i'm having some performance issues with some of the overhead that zend seems to be doing by default.
Given the namespace of my custom library in my application.ini file zend seems to search for same files in it's default library directories before it finally finds the right file it's look for.
Is there any way to disable this or make zend only look in the paths i specify?
Thanks.
This manual page on Class loading performance may be of help to you.
They outline several ways to improve class loading, optimizing your include path, and using a cache to store the location of plugins so it doesn't need to search for them every time.
Hopefully following some of the methods mentioned there can solve some of your performance issues.
I have saved Zend to a folder on my hosting called httpdocs. From what I've read on other questions, I understand I'm now supposed to add something to the php.ini file, and I know it's supposed to look something like the line below. Is the .;c: standard or would it be different depending on my server? If so, how do I determine what I should have instead?
include_dir = .;c:\httpdocs\ZendGdata-1.11.2\library
Thanks in advance,
John
you are probably referring to the include path, which should be set so zend classes can be correctly loaded.
however i take the guess you are on an shared hosting enviornment where you cant do that.
you can. well you probably could it in htaccess but its unlikely.
you can however do this at runtime using the set_include_path functions
be sure not to loose your old include paths, specially "." which refers to the current directory.
however this is very well explained at zend framework manuals, please red the introduction
and also try to improve your accept rate.
I wouldn't use most of the classes from Zend Framework, that's why I'm looking for the thinnest possible ZF configuration.
Is there a better way of finding what I really need other than deleting the whole library/Zend folder, then putting back files based on the error messages that I receive?
I have not used it myself, but http://blog.fedecarg.com/2009/02/01/zend-framework-automatic-dependency-tracking/ may be what you are looking for.
Hm...
There is a lot of information about Zend Framework on SO and with a little bit of reading you would have found the answers to your question
You would also find the answers to your question by just reading the introduction to Zend Framework on the Zend Framework website.
No, that's not how you'll do it. Zend Framework, unlike most/all other PHP frameworks, is rigidly loosely coupled. You can use every component stand-alone. You can only use the loader, or only Zend_Translate. Or you can just use the MVC modules, or Zend_Db, etc.
Of course if you use Zend_Form and want to validate or filter the input, you'll need Zend_Validate and Zend_Filter. But you'll know that because you'll instantiate objects. So just copy into your empty library folder the modules you need. Or even better, copy everything in! A) you won't regret it. B) disk space is not your problem.
What I would do is set up the plugin loader cache and then purge all files apart from the ones called within the automatically generated include file.
zend.loader.pluginloader.performance
I hope it makes sense... :o)