I have developed one heavily loaded project in cakephp 1.3 now my client want it in latest CakePHP version.
I have migrated it using shell script based tutorial provided on below link:
http://book.cakephp.org/2.0/en/appendices/2-0-migration-guide.html
version get replaced it got migrated in CakePHP 2.0 version but now on running a project i am getting an error
Fatal error: Call to a member function parseAccept() on a non-object in D:\xampp\htdocs\arguenet1\lib\Cake\Controller\Component\RequestHandlerComponent.php on line 134
project is mostly developed with ajax functionality and requesthandler componenet also have been used to check isAjax request or not on component side.
Can anyone help me to solve this error...Thanks in advance.
The signature for the __construct() method has changed in 2.x. See the API docs here. Try modifying your AppController::__construct() like so:
public function __construct($request = null, $response = null) {
parent::__construct($request, $response);
// Your code here.
}
Credit to this Google Groups thread.
Related
We use footable in a Asp.net Mvc app. It works fine when running on http.
But when we run thr same app on https from Azure it fails with the error:
(function ($, w, undefined) {
if (w.footable === undefined || w.footable === null)
throw new Error('Please check and make sure footable.js is included in the page and is loaded prior to this script.');
Some ideas?
And what is the best practice for footable in bundles, and where to place it in the _Layout-file?
That error seems to be coming from one of the FooTable extensions (pagination, filtering, etc). The error is likely caused by one of these extensions loading before the FooTable core script itself.
What version of FooTable are you using? It seems likely that you are using V2?
If so, try including the footable.all.min.js as that includes the core footable and the base extensions in a single file
I've created a form with the Jahia Form Builder, but I get this error when posting my form in Live Mode:
Error: org.jahia.services.usermanager.JahiaUserManagerService.lookupUser(Ljava/lang/String;)Lorg/jahia/services/usermanager/JahiaUser;
java.lang.NoSuchMethodError: org.jahia.services.usermanager.JahiaUserManagerService.lookupUser(Ljava/lang/String;)Lorg/jahia/services/usermanager/JahiaUser;
I'm using Digital Factory Community 7.1 and module Jahia Form Builder 2.0.5
Thanks for your help.
Freedomn,
this is actually a bug in the current Jahia Forum and can inly be fixed by using a patched version. See this pull request : https://github.com/Jahia/formbuilder/pull/1
I try to create the entity like this:
DatastoreService ds = DatastoreServiceFactory.getDatastoreService();
Entity stock = new Entity("Stock", 1);
stock.setProperty("Stock", "FCB");
ds.put(stock);
but keep getting the error:
No source code is available for type com.google.appengine.api.datastore.DatastoreService; did you forget to inherit a required module?
The error means just what it says, the GWT compiler needs access to the Java source it compiles to Javascript, and obviously DatastoreService is not something that should exist on the frontend - so you have an architecture issue here.
You'll need to write a proxy that can call a server component (Which in turns calls the DatastoreService) and returns DTOs/value objects (that you define and thus have the source for).
Cheers,
No source code is available
GWT transliterate Java to Javascript, reading it's source code and there a limited language support.
What you're trying to achieve is a Server only operation and you're adding this operation within the client code, which will run on a browser. Neither GAE allow this or GWT has the source of these classes nor capability to do so.
Solution
You need to create a request to your server that will access the DatastoreService , the return the output to the client code.
Below a example of a properly architect GWT web application:
I'm using the JSTreeGrid in an ASP.NET application. The implementation of the JSTreeGrid works fine in the application in which it was designed in tested. However when I moved it over to another application I recieved the following error message below:
Microsoft JScript runtime error: Object doesn't support this property or method
When I initially moved the implementation over I discovered and corrected issues related to the new application forms utilizing Masterpages. The container names were concatenated to the div tags and the scripts were not finding the declared div tag IDs specified in the script. The application that I moved it from did not use Masterpages. I feel resonably certain that the error is related.
The error occurs in the _prepare_grid: function in the jstreegrid script when obj.each(function () section of script is run.
Any insight would be appreciated. Thanks
When you use master pages the Client ID of your DOM elements ia manupulated by the server.
This is due to the chace that you will use the same id both in the master page and in your derived page... when calling Jquery function i would guess that you use id selector i.e. $('#someID').doSomething() ...
When using master one of the solutions is to use the following selector as an exmaple:
$('[id$=myButton]').click(function(){ alert('button clicked'); });
This means that Jquery will select the element with an ID attribute that end with 'myButton'.
for more information follow this post.
How to use JQuery with Master Pages?
I am using the wsdl2objc Tool to generate the soap Searvice APIs for my webservice.
I am following this tutorial to generate code and use it
http://code.google.com/p/wsdl2objc/wiki/UsageInstructions
&&
http://brismith66.blogspot.com/2010/05/iphone-development-accesing-soap.html
I can generate My WebService APIS successfully, but when i added i am getting 8 Errors and errors are
Expected Identifier or '(' before '=' token
Please tell me what can i Do with it. I am stuffed. the WEBSERVICE URL given in the tutorial work perfectly fine when i compile but mine code giving these errors.
Can anybody Help!
First, don't use version 0.6, use version 0.7 instead. I encountered cache problem under version 0.6. The version 0.7 fixed this problem. So, my web service could use session mechanism to store state information.
Second, not any generated codes with wsdl2objc (or gSOAP) and WSDL will be compiled successfully. In practice, our team encountered some problems about compiling, so finally we implemented a proxy web service which provides an interface with simple class types (ex, int, string, byte) in order to avoid the compiling problems.