I'm in a weird situation, my drupal installation on openshift stopped working after a git push(I've been doing git push on this server for weeks and it was woking fine). It just shows the installation profile page as if i was setting up a new website. But when I enter back the info (i.e database name, password etc) it tells me that there is an existing website and shows me the link, but when i click on it, it goes back to the installation profile page.
I have checked on the server all my files from previous website seems to be there...
help plzzz....
First I would check and make sure that your DB is intact. You can do that by sshing into your gear and logging into mysql with $ mysql and then running SHOW DATABASES; to confirm that your DB is still there. If it is you could go a few steps further to check the tables with SHOW TABLES FROM drupal;
Related
Clean Dnn Version : 09.01.01 (129)
When I work with Dnn and have javascript console opened, a lot of times I get error:
/DnnImageHandler.ashx?mode=profilepic&userId=1&h=32&w=32 500 (Internal
Server Error)
At the same time the image in the toolbar profile is missing. Where an how I can see what is working wrong what logs to check? If I go to Manage / Admin Logs and select Log Settings There is a lot of stuf I can enable, but dont know what can be right to see this error and try to find something more.
If I try to open this link in another browser window most of the time everithing is OK and I get generic user image with "?" back.
Also does anyone else see this errors?
Found the same error here:
https://dnntracker.atlassian.net/browse/DNN-9581
It is fixed in dnn 9.2
So I just spent the past hour trying to figure this out, and had to do a lot of cleanup on one of my DNN instances where it was occurring, but once I got all the cleanup done I think it comes down to this.
You're logged in with a Host/SuperUser account correct?
If you login as ANY other user, one of the Users in the Portal, it works correctly?
I ended up having to fix my "profile" page, the site was referencing skins that didn't exist anymore on the profile page, then containers that didn't exist. Once I cleaned all that up, I was able to navigate to the profile page, click on Edit profile, and once I edited the profile, I uploaded a new avatar for the HOST user and was able to get the image to render properly.
I think the issue has something to do with HOST accounts and either referencing an image that isn't part of the current portal, OR HOST accounts and referencing a default image that doesn't exist due to it being a host account, instead of a standard user account.
So how to fix?
Try uploading a profile photo for your account on the current portal and see if that resolves.
I've been tasked with maintaining a DNN site that has been running for a while, so I copied it to my local development environment to get up to speed on the setup. I have the site up and running locally, and I can browse all (I think) of the pages. It seems to display correctly and yesterday, the DNN login worked correctly. However, today, when I try to login to manage changes, I enter my username and password on the login page, but it does not actually log in. On screen, all that seems to happen is that the password field clears. No error message displays. In my Firebug console, the only error message that appears is "Password fields present in a form with an insecure (http://) form action. This is a security risk that allows user login credentials to be stolen." Again, yesterday, I was able to log in and get to all of the DNN management features -- I changed skins, modified CSS, changed code, etc. I've tried multiple logins (host, superuser, and regular user) -- all have the same result.
I don't see anything in the database EventLog, except for a startup record.
I saw a couple of other SO posts tangentially related to failed DNN logins on development environment, and checked that Form Authentication is Enabled in IIS and the security for the site folders are set correctly and the folder is not read-only.
I generally use Firefox for development, but I also tried IE. I'm certain I'm missing sometime obvious, but it has me stumped. Ideas? I'm new to DNN, so I'm not up to speed yet on the best practices for debugging. Any other suggestions would be welcome.
Some details: Live site is SQL Server 2008; Dev is SQL Server 2012. Both sites use IIS 7. Dev is DNN 7.2.2. Locally, I'm using VS 2010 for development.
Couple of things to check.
1) Check to make sure your database connection strings (2 of them) in the web.config are both pointing to your local database.
2) Check to make sure the MachineKey values in the web.config still match the values in the production web.config
3) You might turn off SSL on the site, though you'll have to do that in the database as you can't get logged in. I believe you can likely just set Secure to 0 on all of the Tabs table records, but you might need to track down a HOST setting as well to make this work (hostsettings table)
An update. I was able to get this to work by using a different user account. I'm still not sure what the root of the problem was, but I believe it was related to specific settings on my particular user account. I used a generic 'admin' account, and was able to make it work.
Im experiencing the same issue, I think its something to do with the the .dotnetnuke cookie
It seems that, from Google Cloud Console there is no way to delete a project.
Note: As of 2013-09-19 this is no longer an issue because
Google had fixed it.
- Now you can click on the check box and then
click delete
As 2017 approaches, Raptor's answer pretty much nailed it, but here is a screenshot and the basic steps to delete a project from the google cloud platform.
Go to console.cloud.google.com
Select your project (from drop-down on top nav-bar)
Select IAM & Admin (from hamburger menu on top-left nav-bar)
Click Settings in the left-side-bar nav.
Click SHUT DOWN (image shows DELETE PROJECT)
Enter text per instructions to confirm project shutdown.
UPDATE 11-2020
After clicking SHUT DOWN, you'll see the final dialog popup with instructions on what to type to confirm.
Try to change back to old console design.. You can find delete button there.
This is the old url
https://code.google.com/apis/console/
Then you click in the left sidebar on the project name, you'll have a "delete" link :)
Deleting your project from old console is no longer available!
So in the new console go to Billing and Settings and delete your project from there.
And you are done. Project will get deleted after 7 days waiting period!
You must first disable billing before deleting any project. See link https://developers.google.com/console/help/#deletingaproject
Since the console design has changed, many of the given solutions here won't apply anymore. Here is what Google help says here: https://support.google.com/cloud/answer/6251787?hl=en&ref_topic=6158848
To shut down a project:
Go to the Cloud Platform Console.
Open the console menu Gallery Menu on the top left and select IAM & Admin, then select All projects.
Find the name or project ID of the project you want to shut down, then
click DELETE PROJECT. A confirmation screen describing what will
happen appears.
To confirm, enter your project ID and click Shut down.
Shutting down a project stops all billing and traffic serving, shuts
down any Google Cloud Platform App Engine applications, and terminates
all Compute Engine instances. All project data associated with Google
Cloud and Google APIs services becomes inaccessible.
After a 7-day waiting period, the project and associated data are
permanently deleted from the console.
As of July 2017 the waiting period has increased:
After a 30-day waiting period, the project and associated data are permanently deleted from the console.
As of Dec 30, 2017, this appears to be different (yet again). I did the following.
Logon to the Google Cloud Console, Select IAM & Admin then Settings (from hamburger menu on top-left nav-bar). This is a cascading menu. After choosing that I saw the following.
On the bottom left of the screen is a button/link labeled Manage resources, click on it.
After clicking on it, I saw the following screen, on which I selected the project name I wanted to delete and clicked the Delete ICON/button.
Then I was asked if I wanted to "SHUTDOWN" the project and to do so I had to enter the project ID number, so I did and then clicked on the SHUTDOWN button/link.
Hope this helps someone. The others answers did help me out but were not the exact steps I had to follow.
Important Note: The terms "Shutting Down" a project and "Deleteting a Project" seem to mean the same thing, so if you stumble across something that says "Shutdown the project" you have likely come across another way to "delete the project".
open cmd in google cloud(which can be found after clicking in your project in right top corner) and type
gcloud projects delete [..your-project-id..]
Login with your Google Account
Navigate to this page: https://console.cloud.google.com/cloud-resource-manager?organizationId=0
Select a single project
Click "DELETE" (on top, above projects table)
You may need to visit https://appengine.google.com/, select an application, then go to Administration -> Application Settings, scroll down half-way and click "Disable Application" under "Disable or Delete". One the next page you can also request permanent deletion.
Just found that Google doesn't allow you to delete project in old console anymore. For now, you need to click on project, then "Billing & Settings", you will find delete button there.
Deletion of projects is no longer available under the old Google Cloud Platform Console. To delete a project, open the latest console. Once done, you should be able to see a list of your projects as well as the delete icon(s) on the right side:
You must be a project owner to shut down a project.
It's July 2018, none of the above works. Here is what I spotted and successfully deleted un-needed projects.
https://cloud.google.com/go/getting-started/delete-tutorial-resources
You need to delete all the unwanted project(s) else will be billed regardless.
Answering the question after a long time its been asked. Hopefully it will help someone who is looking for it in 2022.
As per the documentation of creating and managing projects in google cloud. its a simple process.
Search for IAM & Admin in global search.
Once we click on IAM & Admin we will land up in a page as follows.
Go to settings page from the left menu
It will take us to the currently selected project's settings page. On top there is a shutdown button. Press that for deleting the project.
Please note as per the official documentation,
This method immediately marks a project to be deleted. A notification email will be sent to the user who initiated the delete operation and the Technical category contacts that are listed in Essential Contacts. If there's no contact in the Technical category, the fallback contact will not be notified. A project that is marked for deletion is not usable. If the project has a billing account associated with it, that association is broken, and isn't reinstated if the project delete operation is canceled. After 30 days, the project is fully deleted.
Once we press the shutdown button, GCP will show a popup as shown below.
As a confirmation GCP is asking for project id to be manually entered in the popup. Enter the project id with caution and press shutdown in the popup.
It will show the success message as show below.
That's it. Hope it will help someone.
[https://console.cloud.google.com/cloud-resource-manager?project=mapapp-229211][1]
This Will Help For Manage Google cloud projects
To delete projects created using Google cloud console, you can use the following method:
1: Create a dummy gmail account.
2: Add the dummy gmail account as an owner of the project.
3: Login into the dummy gmail account.
4: Accept your role as owner of the project.
5: Visit Cloud console.
5: Go to Cloud Console -> Permissions and delete the main user from the project.
NOTE: Other than Step 2, rest all the steps should be performed using dummy gmail account.
Step By Step to disable and request permanent deletion from Google Cloud Console and Google Appengine Project.
Step 1 - Navigate to appengine project and Click on Application Settings.
Step 2 - Scroll/Find the button to Disable Application. Click the button.
Step 3 - Click on "Disable Application Now"
Step 4 - Click on "Request Permanent Deletion". You will screen update showing the scheduled delete.
Step 5 - Navigate to Google Cloud Console. The status corresponding to the disabled/deleted project is shown as "Disabled" in red.
Go to Google Cloud Platform,
select the project & click "DELETE PROJECT" on top right corner.
https://cloud.google.com/appengine/docs/python/console/?csw=1#delete%5Fapp
There is a current install of DNN on one of my local webservers - this was installed before I took over this position. I am trying to add a second site, but the instructions I am following appear to be for attaching an existing site. Do I simply run the installer to create a new site in addition to the current? I've never used DNN before, so I am going at this blind.
All information I am finding is referencing the same as the instructions link I provided. Any assistance is greatly appreciated.
To add a little bit more information, here is another area where I am confused. Referencing the link, it states #2 to add a binding to my site, then #3 is to add the new portal. What I am trying to do is create a new DNN site - one does not yet exist, so I cannot do step 2 until a new portal is created. As said, I've never used DNN. I was tasked today to have this done by July 4th (nice, huh) so today is the first I am looking at DNN ever.
What I have done is added a new portal and I assumed it would create a new bare-bones site for me, but that is not what happened (obviously). So, instead of just adding an existing site for DNN, how do I add a new one (that is why I asked if I needed to reinstall)? From what I understand, there was an initial website setup with the installation of DNN. That basic site served what they needed - I need to do the same thing again, but, as can be seen, I've no clue how to do so.
No, you don't run the installer again. Remember DotNetNuke is PORTAL Hosting software, meaning with just 1 install you can run ~unlimited websites (of course there's always limits, depending on the hardware you're running on).
For instance if you're DNN install is running on www.myweb.com, and you want to add a site for www.yourweb.com, you simply point your DNS entry for www.yourweb.com to the IP of your DNN install, should be the same IP as www.myweb.com.
You then log into your DNN install as a HOST (superuser) user. You can't do this from using the Admin Login for www.myweb.com, that admin won't have the permissions to add a portal. When you do login as Host, you'll see two more menu items appear, 'Admin' and 'Host'. Admin pertains to functions you want to accomplish ONLY on www.myweb.com, the Host menu applies to the ENTIRE DNN install, including ALL portals you've setup.
Depending on your version number, you probably will see either 'Portals' or 'Site Management' (if it's a newer install, like 6.0+), once you click on or drop the HOST menu.
From there you fill out the specifics regarding your new www.youweb.com website, including the url and any aliases you want. Once you do that and the DNS propegates, you'll then be able to go to www.youweb.com and login and set that site up.
Step #2 is talking about adding a binding in IIS, not doing anything in DNN. You need to tell IIS about strategicplanning.mysite.com, so that it will send requests for that URL to your DNN site.
So, the process looks like this:
Make sure that the DNS record for strategicplanning.mysite.com points to your web server's IP address.
In IIS, update the host header bindings for the current application to include strategicplanning.mysite.com.
a. If you only have one portal in your DNN installation, at this point, trying to navigate to strategicplanning.mysite.com will automatically add it as a portal alias for that one portal.
b. If you have multiple portals in your DNN installation, at this point, trying to navigate to strategicplanning.mysite.com will show an error message about that URL not corresponding to an existing site.
In DotNetNuke, you need to go to the Site Management page in the Host menu (previously called Portals), and use the Manage/Action menu to add a new site. In the form that comes up, use strategicplanning.mysite.com as the alias (keep it marked as a parent portal), and fill in the rest of the details. If you want a blank site, make sure that you pick the Blank Website template (otherwise you'll need to delete a bunch of pages and modules you don't need).
This should be all that you need to do. If you navigate to strategicplanning.mysite.com and you see the original site, then strategicplanning.mysite.com has been added as a portal alias for that site, and you'll need to remove it (in Site Settings under the Admin menu).
So I have moved a good number of DNN database/websites and not encountered the following issue.
After moving and getting the site back up and running, when I try to log into the site with either a Super User or typical user account the following happens:
if I type in the wrong password I get an expected wrong password error
if I put in the correct password the EventLog table shows a successful login, but I am not logged in and it redirects me to the login page.
I have checked that in deed it does not see that I am logged in by going to areas that I can't without it requesting me to login.
I moved the DNN database the same way I have a number of times: backed up database and restored it on the new SQL host server. Updated the portalAlias table entries. The site is obviously up as I can get to it.
Any suggestions?
I would try clearing your browser cache. I have at times had the browser cache freeze the cookie and apparently keep me from logging in or at times from logging out.
I those cases I clear the cache and all temporary files. Then if that still doesnt fix it i break out the virtual machine and try it from a broser on another machine.