Wirecloud couldn't open settings of widget - fiware

I got a instance of wirecloud, I've added there a few widgets, but I couldn't open the settings of the widget in one of them. I've tested the widgets in the fiware instance of wirecloud, there they worked very good.
The problem is that I could click on settings, but it didn't open a settings window.
I noticed that the instance of the fiware seems to be more friendly, I hat to edit the config.xml a few times before my own instance accepted it.
Does somebody know where the problem could be?
EDIT:
After a lot of trial&error I am able to set the settings in the Django-managemenet. So, it seems to be that the options are recognized, but not shown. Do I need to enable them?

Problem got solved by installing wirecloud from the develop branch after commit a6f4125f82 .

Related

Creating an html link to download and install a provisioning profile

I have a download link for an app (ad hoc, only to work on a few designated devices for testing). I have configured my plist file correctly, so the app itself downloads and installs without any issues. However, I think due to it being ad hoc, it does not install the certificate needed to run the app (I currently get the untrusted developer alert, and their is no certificate in general settings for me to trust).
So I tried to add a link for the provisioning profile on the same download page. Clicking on the link in the browser brings up an alert saying that Settings wants to show me a configuration profile. I click allow and it takes me to the Profile area in General settings, but there is nothing there.
How would I go about creating a simple link to download the profile onto the device? The code I used for the link is pretty straight forward.
Profile
Can anybody help? Many thanks in advance.
So I tried to add a link for the provisioning profile on the same download page.
You are not in a right direction. No one will ever do such download profile thing.
For Ad Hoc build, you have to add your desired devices to your ad hoc provisioning profile. I assume you did not do it so you can download the app but cannot install it.
So check your developer certificate portal and remember to re-generate your provisioning profile having these devices checked. And then build the app again with the new provisioning profile.
So it turns out that the issue was when I was archiving the project from Xcode to an IPA file. I was using the default setting for the developer certificate that I should be signing my app with. It also had a dropdown list to select a second certificate (which as far as I can tell is still the same certificate). Selecting the second one seemed to sort the issue out, where as the default option for some reason did not include the certificate with my IPA file. Not sure why it worked this way, to be honest. App now installs and runs without any issues.

Chrome allow file access from files no longer working (was using to see WebGL/three.js files)?

I was using a Chrome shortcut with allow-file-access-from-files in the target to work on my three.js student project files. But sometime this morning this stopped working and it appeared Chrome had been updated. I redid the shortcut but no joy.
Part of the project I'm doing is building three.js animation that works in a common browser (for which I chose Chrome).
Is there any way to get Chrome to allow file access again?
Thanks.
The answer I came up with was to use Firefox instead of Chrome changing the security policy as detailed in https://github.com/mrdoob/three.js/wiki/How-to-run-things-locally
Not a perfect answer but with a deadline looming it's the best workable answer for me right now as trying different variations of Chrome, trying Wamp and also Mongoose didn't work. If I had more time I would work out how to use Python or probably node.js as I've seen it mentioned a number of times as being the faster option.
What gman stated is true, using the Chrome flag (and changing Firefox's security policy) does create a big security risk. But only if you use that shortcut (and it's tabs etc.) for anything other than accessing your own local files. I've been scrupulous about not using it for the internet but don't use this method if you can't be strict with yourself.
Ideally I'd recommend beginning any project with node.js.
Gman's answer is good. If you're in windows environment, and use npm for package management the easiest is to install http-server globally:
npm install -g http-server
Then simply run http-server in any of your project directories:
Eg. d:\my_project> http-server
Starting up http-server, serving ./
Available on:
http:169.254.116.232:8080
http:192.168.88.1:8080
http:192.168.0.7:8080
http:127.0.0.1:8080
Hit CTRL-C to stop the server
Easy, and no security risk of accidentally leaving your browser open vulnerable.
DON'T USE THAT FLAG! You're opening yourself to having your online accounts being hacked and your local data stolen. Here are 2 proof of concept examples
Run a simple server.
It's super simple.
Here's one
Here's one.
Here's another.
And another.
They won't take more than a couple of minutes to download and require no configuration

Why can't I reach Glassfish admin gui?

Either I start Glassfish domain from NetBeans or from the asadmin console, I can't reach the admin panel.
When I navigate to http://localhost:4848, first there's a page saying "The Admin Console is starting. Please wait.", then it tries to redirect to a page having title "Login", but it loads, loads, loads forever. My CPU usage reaches 100% and nothing happens until I stop the server.
I tried Glassfish v3.1, v3.1.2 and also the freshest v4.0, without any modification.
About a year ago, v3.1 worked for me; I have no idea what could happen.
The server log says Glassfish can't find image files.
I uploaded the server log here: http://notepad.cc/share/LvaZvH23sF
I read somewhere that renaming the console-updatecenter-plugin.jar, and the NO_NETWORK=true option can solve similar problems, but these couldn't help for me.
I use JDK 7, and I'm on Windows 7 if it matters.
(edit) Summarizing what happened, from my past comments:
The admin panel was unreachable in Google Chrome and Internet Exlorer.
I managed to reach the admin panel in Firefox, and even in Chrome's incognito mode, but the cause was not AdBlock.
Chrome dev console complained about a 404 error.
After a while, I was able to reach the admin panel in Chrome, in normal mode too, so from that point I couldn't reproduce the problem.
Try access the console in this url: http://localhost:4848/login.jsf
In http://localhost:4848 redirect to http://localhost:4848/common/index.jsf and not work because the url not exists.
I noticed this in your log:
[2013-08-04T10:52:12.761+0200] [glassfish 4.0] [WARNING] [] [javax.enterprise.system.container.web.com.sun.web.security] [tid: _ThreadID=34 _ThreadName=admin-listener(2)] [timeMillis: 1375606332761] [levelValue: 900] [[
Context path from ServletContext: differs from path from bundle: /]]
Following that warning, there are a lot of info messages that the server can't find resources that it expects:
[2013-08-04T10:52:16.495+0200] [glassfish 4.0] [INFO] [] [com.sun.jsftemplating] [tid: _ThreadID=133 _ThreadName=admin-listener(6)] [timeMillis: 1375606336495] [levelValue: 800] [[
JSFT0004: The requested resource (/images/button/primary-mini-roll.gif) is not available.]]
...etc.
I'm curious as to how you installed the Glassfish servers. Did you use the windows installer? If you simply used the installer to update an existing Glassfish installation, an incorrect configuration could have been carried over.
The easiest solution to your problem is to download the ZIP distribution. Extract that to a new directory, start the asadmin tool via the command line and run the command:
asadmin> start-domain domain1
That should give you a completely fresh installation and should work without any problems. There's a good blog post here on getting started with Glassfish 4, it would be worth skimming through to make sure there's nothing you've missed.
not sure if this is still a problem but I got something similiar and I could resolve this by setting an admin password and enabling secure-admin (glassfish 3.1). Not sure if the secure-admin is necessary though, so setting a password might be enough.
download and extract glassfish zip
glassfish3/bin/asadmin start-domain
glassfish3/bin/asadmin change-admin-password (default is user "admin" with no password, so just hit [ENTER] two times)
glassfish3/bin/asadmin enable-secure-admin (might be skipped, just see what works for you)
glassfish3/bin/asadmin restart-domain
Now the admin-gui should be available on http://localhost:4848 and also from other machines via http://your.ip.or.address:4848
Good luck
I've had this happen to me when I enable "Default Principal To Role Mapping":
After I enable this and restart the domain, I'm never able to login again. I had to change the following line on domain.xml (with the domain stopped) :
<security-service default-principal-password="admin" activate-default-principal-to-role-mapping="true" default-principal="admin">
to this:
<security-service>
I didn't find any serious error in your log. Maybe another program doesn't let GlassFish works correctly. For example antivirus.
Had a similar problem.
It happened when I put a primefaces 5.x jar file in my /JAVA_HOME/jre/lib/ext directory and when I removed it all went back to normal.
Through research I found that apparently the admingui clashes with some "3rd party JSF helper stuff".
Hope this helps somebody.
When Running on Chrome you may get this error due to this issue. https://github.com/eclipse-ee4j/glassfish/issues/22439
Admin gui is accessible on Firefox though.
Try this : http://mike.meessen.biz/blog/?p=281
I had exact
first there's a page saying "The Admin Console is starting. Please
wait.", then it tries to redirect to a page having title "Login", but
it loads, loads, loads forever.
problem and it worked for me.
I was in a similar situation and I found that in FF I cannot get access to console but in IE and Chrome with http://localhost:4848/login.jsf I can.
In Eclipse stopping the server and cleaning maybe will help. Afterwards you can access it via http://localhost:4848/common/index.jsf
The solution is quite simple.
There is an apllication/project that you were working on that had some errors. Simply undeploy them using the following procedure:
1.Go to Services tab then Servers then Glassfish Server 4.1
2.Right click on Glassfish Server 4.1 and click on the dropdown to list what under Glassfish Servers.
3.Expand Applications and undeploy all applications to start full receovery of the admin console.
4.Start Glassfish
5.Launch the admin console
Make your domain writeable thats the key guys
it ll work no need to other kinda wierd stuff

Netbeans with chrome integration is not working for HTML5

I am developing HTML5 project in NetBeans 7.3 which will integrate with crome with an extension.But when i try to run the project,it is showing a blank page..please help me. Thanks in advance.
Or this simple check could just work:Bypass you proxy server for local addresses
Check your chrome proxy settings: settings>show advanced settings>Change proxy settings>LAN settings
Check "Bypass proxy server for local addresses"
Re-run the project
Done.
Here is the 100% working solution:
In the menu bar select the Run and in the list move the cursor to the set project configuration:
Which as you can see is disabled, so this answer does not work.
In the list change the chrome with netbeans integration to chrome. It will work definitely. Thanks!
I had the same problem and solved it by removing bad entries in my hosts file (%SystemRoot%\System32\drivers\etc\hosts in Windows).
I only left one:
127.0.0.1 localhost
If you have problems saving the file, try switching off your antivirus' real time protection.
May be you should restart Netbeans|Chrome to changes take effect.
http://netbeans.org/kb/docs/webclient/html5-gettingstarted.html has the setup instructions. Did you install the Chrome extension like it suggests?
Check the hosts file. You should have this line there:
127.0.0.1 localhost
Maybe you have localhost pointed to other IP and the extension doesn't know the right IP address to bind.
Please enable the developer mode in Chrome to make the extension work properly.
I did tried everything but none solve my problem so ended up using Mozilla for debugging, which is pretty straightforward and does not need any plugin to work. Simply change your browser preference from Chrome to Mozilla (in the top bar) and then Run your project.

Unable to get email-ext.hpi to work in hudson

I have just setup hudson and have begun playing around with it.
I have downloaded the email-ext.hpi into the the folder $HUDSON_HOME\plugins
I have restarted hudson post-step1 ( i am following this manual method as i am unable to use (for proxy setting reasons) the automatic way of installing plugins via the "Manage hudson" page.
I dont see any errors when hudson starts. In fact i see the line
INFO: Started all plugins
BUT:
When i start a project configuration page, I do not see the promised option "Editable Email Notification".
FYI:
1. I am able to setup and run few basic test builds and they run fine.
2. I am also able to configure and receive the default hudson emails for failures and subsequent successes.(This confirms the SMTP settings)
3. I was also aboe to setup the subversion tag hpi in the same way as detailed above and that works fine as well!
What am i missing? Thanks in advance for any help!
EXTRA INFO:
Hudson version - 1.379 running on Windows XP
OK - i figured out a workaround (although i still need to dig into why this is a problem). Recording here for anyone else tha tmay face this issue.
The plugin when copied into the $HUDSON_HOME\plugin was somehow not really being activeated/recognized. But when i copied it over also to C:\Documents and Settings\mylogin.hudson\plugins and restarted hudson service, voila! it worked.
If anyone knows why this might have occured, kindly record it here for reference. Thanks.
To install a plugin you should use the easy route. In Hudson, go to 'Manage Hudson' -> 'Manager Plugins' -> 'Advanced' (its a tab) and use the 'upload plugin' option.
Than follow the instructions. Usually you have to restart Hudson to actually get the plugin.
Way saver than messing around with the file system. In general the approach you had should have been correct, but there seems to be an issue with your $HUDSON_HOME. Have a look at the "Manage Hudson" -> "Configure System" page. What is the Hudson Home directory displayed on the top of the page? I don't know what Hudson does if it can't access the Home Directory? My assumption is here that Hudson runs as a service with a user account rather than the local system account and that you used a different account to copy the hpi file.
Install Maven Legacy and Maven3 plugins .