In Orchard 1.8.1 I edited the /wwwroot/Core/Common/Views/EditorTemplates/Fields.Common.Text.Edit.cshtml file. But after uploading the file to the live site all the pages where we have input fields (forms) started to crash.
Throwing "The resource cannot be found." - 404 error.
I had a backup of the file which I downloaded before uploading the changed file.
I re-uploaded the backup file but still the issue exists on the site.
Is there any version mismatch or something?
Any idea what can fix the issue?
Can you paste the changes you had made?
In any case, it is better to make an alternate in your theme, rather than change the view in Core.
Related
I'm trying to use the Joomla ARS. I've set it up and it seems to work for everything except the download of zip files.
I've set it up so that you can see the file in the front end but when you click on it a:
The requested document was not found on this server
error is thrown.
I've tried directly linking the file and it downloads fine. I've also set up an article to check that it'll download and again it works fine. So I don't think there are any permission issues since the zip file can be downloaded just not by using ARS.
Finally I've also tried different file types in ARS and if I swap the zip file for an xml file or a pdf file they both download fine.
Any ideas about how to debug?
I figured it out :)
The site had add a suffix to url switched on which was stopping it getting the correct route. Changed that and it worked as expected.
Before getting too far into developing my theme, which is based on Cornerstone, I have tried running the stencil bundle command and then uploading the customized Cornerstone theme onto my bigcommerce website. It finishes uploading and gets a small portion of the loading bar finished before telling me "There was a problem processing the theme". I'm not sure what I missed in the stencil documentation. Maybe I have made adjustments to a file that shouldn't have been changed, such as the Foundation settings file? If you could help me I would appreciate it.
I put my videos into the cdn folder and it uploaded fine.
Using Kentico 9, while I was away it appeared that something changed! While our production site appears to be working fine our staging site is not. When I try to access the staging site it is unable to "find" any of the related CSS or JS files and therefore displays the site without any of those files. Another part of the problem is that the same thing is happening in the admin portal and since the admin portal relies on those CSS and JS files to work I can't troubleshoot there.
When I try to get to the resource directly in a browser: e.g. iddba-staging.azurewebsites.net/CMSPages/GetResource.ashx?stylesheetfile=/App_Themes/Default/bootstrap.css it fails.
When I try to access it directly at the prod site: www.iddba.org/CMSPages/GetResource.ashx?stylesheetfile=/App_Themes/Default/bootstrap.css as I would expect it provides me the opportunity to save the file.
Our site(s) are hosted in Azure.
Any idea of where to turn next? Thanks.
Also on a possibly unrelated note, I have also noticed an error in the logs on staging that is not on prod:
.NET Runtime version 4.0.30319.0 - Loading profiler failed. Failed trying to receive from out of process a request to attach a profiler.
Not sure if this might be related. Thanks.
Once I realized that getresource.aspx was a dynamic file and the css and js files were either already in the database or were in respective directories it looked at the dlls that power Kentico. In this case I decided to see if there were any differences in the bin directories of prod and staging. I don't know how they became out of sync but they had. Since the problems I had appeared to be serving up CSS files I noted that one file CMS.LessCss.dll was in prod and not in staging so I copied that file in. As soon as that file was copied Kentico threw an error with the word Jurassic in it (odd!). I found a file Jurassic.dll that was in Prod and not in Staging so I moved it.
Voila! The site was back, serving CSS and JS files on the front end and in administration. We are still clicking through all our pages to see if anything else is not working but for now we are good and if I have any further questions I will look in bin first since there are still files that live in prod that are not in staging and I don't want to re-populate unnecessary files. I am just not sure how the directories got out of sync in the first place... or at least no one here has admitted to having messed around! Yet.
Thanks for all your help.
we have a XPage project in the Domino Designer. The project contains a file [database.nsf]/Code/Java/META-INF/services/com.ibm.xsp.core.events.ApplicationListener, which configures an com.ibm.xsp.application.events.ApplicationListener2 (same with com.ibm.xsp.application.events.ApplicationListener) to be executed when the application is created, refreshed and destroyed.
When I clean and rebuild the project I often get the following error in the problem section:
The project was not built due to "Resource already exists on disk: '[database.nsf]/WebContent/WEB-INF/classes/META-INF/services/com.ibm.xsp.core.events.ApplicationListener'." Fix the problem, then try refreshing this project and building it since it may be inconsistent.
This message is correct: the file is than available at that location. (You have to use the Eclipse view "Navigator" to see it, because the directory /WebContent/WEB-INF/classes is hidden in the project explorer.). When I open the file, it is empty. When I open the properties of the file, the size is "-1 bytes" (yes, minus). When I delete the file and refresh the folder in the Navigator, sometimes the file come directly back again with size -1 bytes, sometimes not. Sometimes the bug is solved after next clean project, but sometimes it reoccurs.
When the Designer compiles the project without error, the file has the correct content. At runtime this file is read and the ApplicationListener is executed, all events are fired as expected.
When the error occurs I could copy the content by hand into the problematic file and save it, delete the error task in the Domino Designer. Than the application also works fine (?).
I tried to create a minimal example, with a new project (nsf database) with only the configuration file (/Code/Java/META-INF/services/com.ibm.xsp.core.events.ApplicationListener) and the application listener implementation. Unfortunately the error does not occur.
The reason may be, that our project has a lot of files. We had this problem only with the services definition file. The problem also occurs when I rename the file (I appended two underscores as test).
The problem occurs with Domino Designer 9.0.1 and Notes 9.0.1 FP3.
Our project has an associated on disk project. But I had the same problem after removing the association. After associate again the problem was there again.
Is there a solution, except removing the file? (Whithout the file our application will not work correctly.)
Thanks in advance
Stephan Koops
I have had the same issue. In the 'Problems' view it lists 'The project was not built due to "Resource already exists on disk .../WebContent/WEB-INF/Classes/... then a file with a long hex name ending in .js.
Even simple Xpage changes would not appear on the browser no matter what I did with clean/build etc
What I find works is:
Open the 'Package Explorer' view, and in the first Folder called Local you will see a series of *.js files as mentioned above.
Delete them all.
Clean and build.
Bingo, my xpage is now working again.
I'm having problems uploading and even viewing files in the File section of MODX Revolution 2.2.3-pl. When I try to upload a file, all I get is "Upload error". Nothing shows up in the Filesystem area, just a folder called Media that doesn't let me do anything. Any ideas of what might be going on?
As far as file system permissions go, all folders are set to 755 and all files are set to 644. I'm seeing this behavior logged in as admin/sudo. I just moved my installation of MODX from my local machine, where I believe it worked right, to a shared hosting environment, and that's where I'm seeing this issue.
There has been a recent update to 2.2.4-pl after reported problems with the file manager.
I'd recommend updating to 2.2.4-pl and check if the problem is still present.
Also it could be that your MOD system settings have Use Multibyte Extension enabled but PHP hasn’t been compiled with the –enable-mbstring option.
Hidden away in the MODx Media Browser is a failed response to a JSON request and an error message showing…
Fatal error: Call to undefined function mb_strtolower() in on line 168
If you can’t recompile PHP or just need to get your Media Browser working again, go to System Settings and set Multibyte Extension to No.
All the credit to [Max Mitchell's Post].1