I'm trying to follow the steps described on https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-a-python-app/#configuration to configure Airbrake for a Django project. In particular,
To configure pybrake you will need your Airbrake project’s id and api_key, these are available from your project’s settings page.
I'm browsing around on the project's page on airbrake.io, but for the life of me, I can't find any "settings page". How do I find these keys?
According to Airbrake's tech support, the "Settings" tab is not visible to non-admin users. However, the project ID is simply the number in the URL.
If someone uses it.
On your project's dashboard look for the top tab called Settings and then top to the right you'll see the info
Related
I am working on a website created in PHPRunner. I have created a page using custom view and added it in the side navigation bar using Menu Editor. But when I save & build the project. I am not able to see the page I created on the website. The software doesn't show any errors when I build the project. All I can see no changes for the new page on the website. I am not sure whats wrong with the software or how to trace for errors?
Can anyone help me?
You need to give the group permission to see that page from the Administrator rights section.
My first DNN site. Please go easy.
I'm trying to load some extensions (Blog & a PayPal extension).
While the admin console show's they're installed I can't see them or start them. They are not evident on any of the menus.
The theme creators say its not their problem.
Any suggestions for a Newby on how to get the extensions working?
thanks
You actually need to go to the page where you want a module to live and then use the Modules admin menu entry to Add New Module to the page. Click the menu entry, and you can drag and drop a module onto the page.
Yes.
They're listed and "In Use" is recorded OS "No"
OK - here's a screenshot of the Admin Page in Edit Mode whilst loggedon as a Super User after an Extension Module has been added to the page.
As you can see:
The extensions are not showing
Instead the area on the page shows 'Banner Options' even though no banners were inserted.
You are on the Admin page, and it certainly looks like you have added two modules to the bottom of the page. One of them seems to be the Banners module, as the screenshot shows that mousing over the edit pencil icon shows the Banner Options.
My guess is that this isn't close to what you want to do.
I think that what you want to do is to add a module or modules to some other pages.
So, go to the page to which you want to add a module. Then, click or mouseover the Modules menu item in the admin menu. Select a module and add it to the page.
Does that make more sense?
I would like to add functionality to the AtTask system by "adding a layer".
What I want to know is whether this can be achieved with a plug-in for Internet Explorer.
To give a concrete example:
This extra layer would allow users to click on "Online Edit" document (which is not available right now). The linked application will open, and when you click save, the file is loaded back to AtTask.
All this happens in the background via the AtTask API, and is transparent to the user.
The question is: is it possible to add functionality to a site by somehow adding layers?
Last comment: this plug-in (or whatever needs to be installed inbto the browser) will only be visible/active when accesing the AtTask website.
Thanks in advance for your responses.
Within the confines of AtTask your best bet is to use an "External Page" create a service that handles the data in the manner you need.
The Dashboard that contains your External Page can be added as a tab via Layout Templates.
Most of the heavy lifting would have to be handled by your application. You would have to link the document(s) you wish to edit.
Some sort of referrer would be necessary to place the revised document back into AtTask. The method in which the client can do this would be determined by your preference and requirements. I am sure you can find some sort of Wiz-Bang jQuery uploader.
Depending on the level of control you have with your user base, you could make an Application URL
Windows : Registering an Application to a URI Scheme
OS X : Launching Scripts from Webpage Links
I do not know of any other way to handle this other than what Steve suggested.
Having said that a possible solution to this is to create a new application and iframe in AtTask.
At the top or wherever on the page your application could have a link for "Online Edit". Then you would use javascript to extract the task id, project id or any other needed information you need for the api to get the needed content to edit. Then save using the same api information.
I have not tried this type of method but theoretically it could work.
I don't know where I need to register my app after created my first project. I already followed their instruction regarding to app registration.
https://cloud.google.com/console
To register a new application, do the following:
Go to the Google Developers Console.
Select a project, or create a new one.
In the sidebar on the left, select APIs & auth. In the displayed
list of APIs, make sure all the APIs you are using show a status of
ON.
In the sidebar on the left, select Registered apps.
At the top of the page, select Register App.
Fill out the form and select Register.
Thanks a lot in advance.
The instructions you pasted refer to the older API Console.
You can either figure out their Cloud Console equivalents (Create Project, etc), or go to the previous version at https://code.google.com/apis/console/b/0/?noredirect
It's worth pointing out that Google's terminology is somewhat muddled. Sometimes "app" refers to a "project", other times it refers to a "client" within that project.
For example, you might have a project called "My Multi-Device Task List". That may have a web client, an Android client and an iOS client. Sometimes the word "app" refers to the project, other times it refers to one of its clients.
I have installed both author and publish instances of CQ5.5 on my PC. But when I add a new page and publish it, it does not appear in the publish instance. Only a blank page is rendered.
I have tried activating it both from the siteadmin and from the Replication page in Tools. Only the navigation item appears in the Publish instance.
I checked the Request logs also. But it only gives a
200 response(OK)
Can someone please help me on this ?
You need to activate/replicate your /apps/site folder where all of your templates and components are located to push it from your author instance to your publish instance. Activating a page doesn't automatically activate the components and templates it uses.
Go to:
http://localhost:4502/etc/replication/treeactivation.html
Browse to or type /apps/[your site] in the path field
Set the check boxes to fit what you want to activate (Unchecking all will make everything under the selected path activate)
Click 'Dry Run' to see what will get activated without actually activating. (This is more of an informative step to help ensure you don't activate something not intended in a production setting)
Click 'Activate' to activate.
You can then check your publish instance to see your templates and code are there.
It is easy to miss activating your apps folder as there is no ui like the website admin for pages where you can activate.
Activating a page/folder/asset does not activate sub-pages/folders/assets. This can cause confusion especially when working with folders.
Generally if you need to activate a tree the best way is to use the tree activation utility
The only time I've ever seen this is when the code is not installed. That would be the first thing that I'd check. Go to (assuming you have your publisher on port 4503)
http://localhost:4503/crx/de
You should have your the code in /apps and you should be able to find the content page in /content too.
The reason this happens is that the sling:resourceType property points to a component that doesn't exist so it uses the default which is an empty output.
You have to build the code to both the environments (author as well as publish). This way both the environments will have the same copy of source code installed in the form of cq5 packages and felix bundles. Then if you create a new page or drop any component on any existing page, it will appear the same on publish environment after activating the same either through 'Activate Page' link in sidekick or through replication tree activation page.