I'm currently working on migrating an old webpage (example.se) into an existing plone/zope installation (example.net).
The "new old webpage" which should be integrated should:
share the same functionality as the existing one
share parts of the content in both directions, e.g. like papers or collections
example.net currently serving two languages, de and en (example.net/de, example.net/en).
The old webpage only uses english and (currently) no subfolder is used (example.se/)
The domain names should stay as they are to access the webpages.
The solution I'm heading to so far is to create a new seperate instance for the new webapge.
Even if they are seperated, the functionality can be easily shared by using the same buildout scripts.
However sharing content would not be possible, only by copying them over manually (thus, adding new content twice, which should appear on both pages)
Is there a way to archive this?
I'm using plone 4.1.6 and zope 2.13.15.
Related
I have downloaded an Umbraco 6 site and I have tried replicating the environment locally in my machine, using the production database and the compiled site from production.
If I go to the Umbraco backoffce and to the Settings => Dictionary entries, I can see a specific dictionary entry in multiple languages.
This entry is displayed correctly in production when the user chooses a different language. However, locally, when I change the language, the dictionary item still appears in english (the default language and does not get translated).
I have tried running the site through Visual Studio and WebMatrix, to check if this was some issue with the webserver settings locally, as this might be session related, but the issue still happens.
Is there a reason why translation for dictionary items is not working as expected? Content that is created through nodes and translated there is showing up in the correct language, but dictionary items are not.
UPDATE
I am now looking into something that could be responsible for this. When I am at the content area and select one of the language nodes and head to properties, I see multiple "Alternative links", which contain URLs to the same page on different domains. I don't see localhost:XXXX/EN.aspx there, which makes me wonder as to whether or not the site is handling the language detection correctly in localhost. I haven't found how to add additional links there, and be able to use a wildcard for port would be interesting.
You should right click on the node - select "Culture and Hostnames" and add your domain there.
After that right click on the root "Content" node and click on "Republish entire site" - that should clear the cache and you should be able to see the new url under "Alternative links".
We are using umbraco 7.1.3
As per client's requirement we need to create more then 550 Umbraco CMS sites for different cities with same template and asp.net user control which access data from one master database.
So we created one windows application that will create 550+ sites as per city name under one Non-Umbraco root site.
We also managed to create different Umbraco database for each site is created and moved published code under to Non-Umbraco root site and convert to application and also updated Web.config file for each site dynamically.
After that when-ever we found that our logic or UI was not correct we also update DLL, ASCX user controls and CSS to all sites through same window application.
Till now everything was going smooth, but now we have one major change and that contains new document type, template, macro and new menu needs to be added dynamically. Updating published code through windows application was easy but we don't found any way to make update Umbraco database of 500+ sites through another application.
Some websites are already updated through respective sites owners, so without affected any existing changes we need to add new macro, content, document type and menu for each site and we don't know in which Umbraco database we need to enter records?
Had already posted the same in umbraco issue tracker #U4-7105
Also in Umbraco forums #71443
Thanks & Regard
Sounds like an interesting case!
If you want to migrate items that are in the database such as document types, templates and macros you would most likely need to get a product like Courier. I can see that due to license costs this could be an issue for you with 500+ sites.
Another option could be to take a look at uSync to see if it does what you need. I don't have much experience with this package but from the looks of it, it seems like it is handling all the database bits - and everything else (files on the file system) would be handled by your application just as it is right now.
ASP.NET 4.51, MVC 5
Have read Integrating a CMS into an established application-centric MVC website
We have a number of MVC applications that serve as public facing websites. The applications were built using MVC as that was the technology stack understood by the developers and primarily the content that was being delivered was based on business process data.
However more and more we are being asked to add "another page" to the websites which for all intents and purposes is a plain old static content page. This ultimately involves:
Adding a new route
Creating a view with the required HTML
We have various "home grown" solutions which now pull HTML from the database for these views. However this means we are writing custom back end data entry screens as well as 1 & 2 above.
So.... There must be a better way. Has anyone got any practical experience or suggestions on how to add simple CMS functionality that we can give to end users, plugged into our MVC application? We need to provide the following functionality to the end user:
Create new pages, edit pages using WYSIWYG
Add meta tags and canonical tags for SEO
Specify the url portion of the uri for SEO purposes
All insights appreciated.
Is it feasible to do the following:
Have a database table to house the content for these pages. e.g. title, summary, description, url, meta, image(s) etc...
In the front end have a template for these pages. The database data fills in the placeholders within this template.
Perhaps hold all the pages on a base URL like www.yoursite.com/page/dynamic-page-url-from-db
You can use the Remote attribute validation on the url field to make sure they are all unique in the database.
With this in mind, create a single Route to catch the requests and filter valid/invalid requests in the Page controller based on the URL provided with the db. If non-existent throw new HttpException(404, "Page Not Found"); and have an error handler pick that up and deliver your 404.
META could be set via ViewBag or a dedicated section that alters the _Layout file at the point of rendering the view.
TinyMCE is a decent WYSIWYG editor. You can even add dynamic image gallery functionality to it if you want to embed images within the main body of the pages.
I'm working on making a CMS currently used in a demanding production environment into a product. I've just (as of 20 Jan 2015) made a NuGet package which installs the CMS into an MVC project which should be possible to add to any existing MVC site without breaking it. CMS functionality can then be added where needed. Currently I'm looking to work with some users to help them get the CMS into production on their sites, however this may have changed by the time you read this. Look at http://www.lynicon.com for more information and to sign up to a Slack community where I can give you access to the NuGet package.
Company I work for have a site developed 6-8 years ago by a team that was enthusiastic enough to use their own private PHP-based CMS. I have to put dynamic data from one intranet company database on this site in one week: 2-3 pages. I contacted company site administrator and she showed me administrative part - CMS allows only to insert html blocks & manage site map (site is deployed on machine that is inside company & fully accessible & upgradeable).
I'm not a PHP-guy & I don't want to dive into legacy hardly-who-ever-heard-about CMS engine
I also don't want to contact developers team, 'cos I'm not sure they are still present and capable enough to extend this old days site and it'll take too much time anyway.
I am about to deploy helper asp.net site on IIS with 2-3 pages required & refer helper site via iframe from present site. New pages will allow to download some dynamic content from present site also.
Is it ok and what are the pitfalls with iframe approach?
This is the second "I'm stuck with a legacy CMS, and fixing it would be too hard" question I've seen here in the last day. I really don't see what the problem is -- I've done this in less than a day:
Pick any modern CMS and see what tools it provides for importing pages. Spend a little time learning how it stores pages. (I chose Wordpress).
Backup the CMS database.
Run a web-spider through the old system and dump all of the pages to disk as plain HTML.
For each page that you saved:
Run HTML Tidy on each HTML page to make it more uniform.
Run it through sed or perl or write a custom program (say, python with BeautifulSoup) to separate out the page content from the (no longer needed) navigational cruft.
Insert the content into a new CMS-managed page (ideally by inserting a new row in the CMS database).
Review the site and manually clean up anything that wasn't caught in the conversion.
A little bit of shell scripting can automate most of this -- just keep refining your scripts until you get most of it 'right'. If you backup the CMS database before you run your script, you can reset the site to 'empty' for each import.
(In my case, the site in question had been in use for ~10 years, with a succession of webmasters, each who used different tools and techniques for managing content, and had been hacked a couple of times by spamvertisers.)
Admittedly, this isn't a science, and it may require you to learn some new tools. Go for it -- learning new stuff is good for you, and you won't have to keep that old server running for the next 10 years, just so you can wrap its content in an iframe.
These folders appear in my .NET Web project. Why do they appear? Are they useful?
They are used as part of the FrontPage server side extensions which do
change tracking (mostly the _vti_cnf)
code/script used by FrontPage specific controls (mostly the _vti_script)
general settings
The old FrontPage program and Dreamweaver both used it.
The VTI part is actually because FrontPage was originally created by Vermeer Technologies Incorporated (note the acronym) and then bought by Microsoft and it just stuck.
They're part of the legacy FrontPage server extensions. The _vti_ prefix refers to Vermeer Technologies Inc., the original developer of FrontPage which was subsequently bought by Microsoft. They would appear if you installed these IIS extensions - they're not needed unless you have a legacy client which requires FrontPage extensions to be there.
Expression web also uses them. In particularly the “_vti_cnf”, “_vti_pvt”. Do not delete them. The “_vti_cnf” holds your meta data. If you delete it, you can rebuild it by Recalculating Hyperlinks. You will find one in every folder.
Delete the “_vti_pvt” will cause you problems, in recognizing the local website. You should only see this in the main folder.
If you have problems with updating the web server (EW or FP incorrectly uploads files that have already been updated), do not delete the contents of the _vti_cnf folder. Usually, just recalculate the hyperlinks via EW or FP and that will take care of things.