I have a website built with TYPO3. (www.fibo-nrw.de) I moved this site to a different server with the same name (without changing the domain). I have transferred all files and databases in full. Currently I can access the backend, I can see all my files, but I cannot view the site. Where could I be doing wrong? My TYPO version is 6
Related
I am new in website development using Static site generator and Cms, I am developing one static website using eleventy SSG and Strapi CMS.
All my contents are stored in CMS.
(I Assume all you know about SSG and CMS). Now I have doubt about contents, suppose, I update my contents then it will automatically reflect in my static site without restarting eleventy server or should I restart my eleventy server.
In my current project, When I update my contents using CMS, My site not updating their contents but if i restarting my eleventy server then it is updating.
Is it right to restart eleventy server after update contents or is there any way available to update contents on website without restarting eleventy server.
Please guide me.
SSG involved that content is "statically rendered" to static files. So, you need a mechanism that fetch new content from Strapi and adapt your files or your displayed content.
Here are some ways to do it:
Restart Eleventy server (but it causes downtimes)
Fetch fresh Strapi content using frontend code (but it could be slower and bad for SEO)
Do not use SSG if your content is often updated. Prefer more flexible tools like NextJS or Remix that handle SSR or hybrid behavior.s
This may not be a straightforward answer.
Anyway,
I am using Eleventy as a Static site generator.
So, I have installed #11ty/eleventy using npm.
This restarts my eleventy server everytime I make change and logs the errors if I have one.
I have a client site as a published dnn website hosted on a local server in the organization's premises.
I have developed a new module using the source code that fetches data using a stored procedure.
This is what I did to transfer the changes to the live site
1. I created the stored procedure manually on the live sites DB,
2. I published the site and replaced the content of the website folder with my published site.
3. I added the new module in the live site using the "Module Definitions" option found under the "Host" menu
Everything works perfect in the development environment, but When I publish the site and do the update on the live server , the module returns no data as expected.
Can someone guide me through how to moves the stored procedure and my new published site to the live site.
I would recommend creating your module as an installable zip file including SQL for creating the stored prods and any other db changes required.
There are a number of tutorials around that will help with this and the templates build by Charles Nurse are a great help in getting your head around good practice. (http://www.charlesnurse.com)
In the mean time have you checked the permissions on the SP in the live database. That may well be your issue.
James
Tried the recommendation on several threads. Here is the issue. The admin is working and updated the new DB fine. When you view the site from the frontend the product data, images, and links all point to the original site.
I Began by creating a new DB and importing a back up of the other Magento DB. The DB has a different name, the login and pw are different as well.
I modified the secure and unsecure URLs in the core_config_data table. I then installed a fresh copy of Magento (same version as my old site ver. 1.7.0.2).
I emptied the log tables which contained the old URL as well.
I looked at the local.xml file which had the correct settings.
Please keep in mind I have not added any source files from the old site. The olny thing that is from the old site is the DB.
Any other advice would be huge! Thanks in advance.
I never could get to the bottom of it. I simply uploaded fresh install of Magento and imported the data and it worked.
I have been trying to run a symfony project I created recently using symfony 1.4.
But pointing to the url (xyz.in) simply shows up the directory structure of the application
In the CPanel I have edited the document root to be upto app/web/ directory
After doing this all I can see is a blank page and nothing else.
What might be wrong? What are the necessary steps for deploying a symfony project to a shared hosting?
You can check the rights on cache and log directories, Apache needs write rights. Ther are many problems with symfony and shared hosting, but it's not an impossible task.
I have a DNN site (5.06) that I developed on a standalone machine running IIS7. When I copied the site to the production machine running IIS6 and enter the URL, such as www.site.com, I get a generic DNN error page with no additional information. However, if I add the default page, www.site.com/Default.aspx everything works fine.
The Friendly URL settings were never changed and I've verified Default.aspx is entered on the Documents tab in IIS6. The portal event viewer has no entry for the error page I get.
I'm nearly certain it has to do with migrating from IIS7 to II6; clearly I'm missing something here. Any ideas?
DNN has confirmed this is an error in 5.06, and will be addressed in a future update. That doesn't help me today, but I was able to work around the problem by adding the following to the Friendly URLs list:
Look for: .*/
Send To: ~/Default.aspx
I can't find the forum thread I was reading yesterday, but did find this one which also goes into detail on the issue: Error upgrading from 5.5.1 to 5.6.0
Pretty odd...
Double check PortalAlias table in your SQL server. Confirm www.site.com is in there.
Double check host headers in IIS6 has www.site.com
Make sure Default.aspx is in the documents area of IIS6 and set as the top default to run
Recycle your app pool
cross your fingers
Only thing I ever run into from IIS6 and IIS7 is in the app pool running in Integrated mode or classic... but that is usually as issue going from IIS6 to 7, not vice versa.
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have the correct machine key and connection strings. This is my last resort when DotNetNuke is being strange. I am running 10+ DNN sites at version 5.6.0 and I only encountered this issue once.