noeticpenguin/angularvisualforceseed

This project is a "seed" project for using Angular 1.3 on Salesforce.

angularvisualforceseed's Issues

Winter 15 Release - Causing failure

Can you think of anything in the latest Salesforce 15 release that would cause a conflict or stop Angular from fully initializing or bringing in any of the visualforce pages defined in the routes ?

I am 99% certain that the update is causing the issue. I have confirmed this in 2 two different orgs by refreshing the sandbox and it works as expected, overnight it updates and it no longer works.

Background:
I have started several different projects in different Salesforce sandbox orgs, and on a new refresh and only adding/updating the basics(custom settings, routes, visualforce pages for routes, and dummy content) everything works perfectly as expected.

Problem:
However as soon as the Sandbox is auto-updated to the Winter 15 release the seed App does not work. It doesn't seem to initialize, I have confirmed that all resources are available for both cases local and server side via chrome developer tools. There are zero javascript errors, and it seems to recognize the seedApp visualforce page, and it brings in the angular_config page with a session id and the resource URL. It seems like the Routes are never initialized to bring in any of the other visualforce pages defined. Also, using the ng-Inspector(chrome app), it only shows the app name(seedApp) and $rootScope with nothing underneath it.

If you have any idea of what could cause this please let me know, this has me stumped. I have learned a lot from this project, and I plan to write up a tutorial for others as well as contribute. I would be happy to grant access to the Sandbox to give you a full view of the project. I just refreshed one of my other orgs Sandboxes that stopped working, and I do the bare minimum setup again to have a working example for comparison sake and post the code on Github and/or grant access.

Please let me know if there is any other information that I can provide.

Thanks,
Nick

ngForce vfr error

After installing the unmanaged package, and running through some proof of concept work, I ran into an issue when calling the pre-defined vfr method below, and I noticed that ngForce(ngForce-visualForceRemoting.js) source was out of date compared to your ngForce repo. I tried other vfr methods including calling the controller directly with .send(), but the results were the same.

vfr method - Errors is created by the first line in the snippet.

var propType = vfr.describePicklistValues('pba__Listing__c', 'pba__PropertyType__c');
propType.then(function(results){
    $scope.propertyType = results;
});

Before attempting to update static resources with the new version of ngForce, I would get the following error:

Uncaught TypeError: undefined is not a functionngForce-visualForceRemoting.js:93 (anonymous function)VFRemote.js:132 e.cbVFRemote.js:99 VFExt3.direct.RemotingProvider.VFExt3.extend.doCallbackVFRemote.js:94 VFExt3.direct.RemotingProvider.VFExt3.extend.onDataVFRemote.js:75 VFExt3.extend.handleResponseVFRemote.js:39 aVFRemote.js:40 (anonymous function)

After updating ngForce(ngForce-visualForceRemoting.js) manually I get the following error:

 Uncaught SyntaxError: Unexpected token &

Thanks for putting together/sharing the seed and ngForce projects. They are both a huge help to get going with angularJs and SF in structured manor.