I think I've noticed a problem in Sencha Architect whereby the app.js views collection property is not updating. I've removed all my views and added 2 new ones, but the views array is not reflecting what views I really have in my project. Seems to be losing track of what it has somehow.
Has anyone noticed this? Is there a fix or work-around for this?
Try restarting Architect. If the problem persists, check to see if you have added all your views in the "view" config under "Application" in your inspector.
For me a restart didn't fix it (in Architect v2.2.3) so I closed Architect and manually edited the metadata/Application file to remove the defunct views and then they were gone when I restarted Architect.
Related
I'm using IBM Domino Designer 9.0.1. I have a server locally installed, and I have an ODP project associated to the nsf. Recently I've been opening Domino Designer to have it completely forget the nsf elements (have a look at the picture). Preferences/General/Workspace is set to 'Refresh automatically' and Build automatically is turned off.
I've tried: Refreh (no effect), Build (no effect), Sync (Progress bar gets filled with 'Updating File Menu based on Navigator Filter' but no progress).
The only thing that seems to work is re-associating the ODP to a new nsf.
Anybody have anything similar? Should I just reinstall Domino Designer? Because, you know, that's just loads of fun!
I had a similar issue but with an older version of Designer (8.5 or 8.01). Currently at 9.01 and haven't had the issue. I believe I had to rebuild my /workspace to solve the issue.
I found another similar issue with 8.01 in the Notes forum. You didn't mention if Processing indications (green circle and status bar bottom right) showed anything going on in the background.
delete your workspace directory under Data. it saves your day
Using Liferay 6.1 CE GA 2 I have added portlet to page. Recently I have faced the following issue:
When I click on Options > Look and Feel I receive "You do not have the roles required to access this portlet."
But I am using admin account, how can that be? Let me know if there are any ideas.
This is an old issue but I thought this answer might help others as it was a pain to figure out. I had this exact same issue and found it was caused by changing the value of the portlet.add.default.resource.check.whitelist property in portal-ext.properties. Somehow modifying this list made it so that I couldn't access the Look and Feel menu of any portlet, I always got the "You do not have the roles required to access this portlet" error. Upon commenting out the portlet.add.default.resource.check.whitelist property I was able to once again access the Look and Feel menu. I have a embedded portlets in my theme that need to be on this whitelist so I was worried that the Look and Feel menu would be broken if I added the property back, but apparently Liferay was just caching invalid permissions and removing the property cleared them because I was able to add the property back and restart the server and everything worked fine.
I faced it once and hence had put below things in portal-ext.properties and it started working. Also, remove the portlet once and reconfigure it.
theme.css.fast.load=true
theme.images.fast.load=true
javascript.fast.load=true
I am having an issue with Designer 8.5.3 crashing when I try to drop and drop fields from the data palette on to a custom control or an XPage. Occasionally the drap and drop will work, but with no apparent reason or consistency. Most of the time(98%) designer crashes.
I am currently using Windows XP on a corporate imaged laptop.
I have errors similar to the one below listed for the databases that I have tried to work with.
The project was not validated due to "Can not create a Resource at the location : jnsf:/Local/databasetest.nsf/bin". Fix the problem, then try refreshing this project and validating it since it may be inconsistent databasetest.nsf Unknown JavaScript Problem
I have read a related post and tried the suggestions, but they did not seem to work. Any help or pointing in the right direction would be greatly appreciated!
Have you opened a PMR with IBM yet? If not, do so an supply them the crash logs, dumps, ...
I have been trying out Redmine to see if I like it better than mantis. However, I am wondering if it possible to modify watchers of a bug after bug creation. As a project manager, when I create a bug, I can select users to have watch a bug, but after I create it, I don't see a way to edit this list. Does Redmine have support for modifying the list of users watch a bug? If so where?
Of course you can edit this list - if you have the necessary permission, there should be the list of watchers at the right hand side of the issue's detail page, with a link to add watchers opening a dropdown list.
I am developing publishing site. I have some layouts that are pre-populated with web parts and have a problem when I need to make some change on the layout.
Deployment succeeds but I still see old version. If make I change in SP Designer it is reflected OK but not if the change is done by the feature that is being deployed.
It looks like after I deploy particular layout any site collection in that web application will have the first version.
I have tried deleting complete site, all the pages, layouts and nothing happens, after deployment I still see old layout.
Current solution for this problem was that I take new virtual image and start with clean machine.
Real problem is how to solve this on clients installation without reverting to clean machine. There will be some bug fixes and I will have to send new WSP file with some changes in layout.
Is there any way to force SharePoint to use newly deployed layout and not some old Unghosted version?
If the layouts are without web parts I don't have this problem.
Update
I am using default "Publishing Portal" and deploying layouts using features. For development I am using VSeWSS 1.3.
tried in SharePoint designer to detach page from layout and attach it again but still no results.
Since you are using VSeWSS, you can execute your own code upon feature activation. So try writing an SPFeatureReceiver that will call SPWeb.RevertAllDocumentContentStreams() to reghost directly after feature activation on the web(s) in question.
If this doesn't work, then the problem isn't about ghosting, maybe it's about Orphans then. But try this first.
If it's a feature that you are deploying you have do deactivate the feature and activate it after deployment again. And don't forget to do an IISRESET or an AppPool recycle.
If your new site collection has the first version of the layout make sure that it is really your new feature version that you are activating.
Try to reject your solution first and add the new one after that.
Are you using Site Definitons or Site Templates? If you are using either of these it may not update after initial provisioning.
Try completely retracting and deleting the solution from central admin, resetting AppPools and then redeploying the solution.
Make sure your element manifest for your feature specifies that existing files should be overwritten.
Looks like some folks have had problems with layouts too...
See http://msdn.microsoft.com/en-us/library/ms459213.aspx
If you are developing new sitedefinition, you can attach your new layout in the onet.xml file by using the property, i hope it will help you
-->