I'm installing a TYPO3 installation from a website that already uses TYPO3.
These are the steps I already have done:
I installed a blank TYPO3 installation.
I copied the contentapi and contentelements from the existing server to the typo3conf/ext folder on my server
I imported the data from the mysql TYPO3 server of the existing database
When I log in to the TYPO3 webpage, I have no templates configured and have a few issues. I tried to fix them by searching on internet but didn't find something clear.
On the pages tab I only can see this:
in the log files:
The error is sending me to this page:
https://wiki.typo3.org/Exception/CMS/1294587217
I already did that, but didn't help, or I did it wrong
On my templates tab there are "no templates":
If someone can guide me to a next step, that would be very helpful.. thanks!
root template:
plugin.tx_ahcontentapi.settings.auth.user = bm
plugin.tx_ahcontentapi.settings.auth.password = sdfsdfdsf
plugin.tx_ahcontentapi.settings.url = https://sdfsdfdfs.com
plugin.tx_ahcontentapi.settings.https = 1
tree-view:
Web server root folder:
(laravel application is the green selected folder, with views,language files,..)
did you have all Extensions installed?
typeNum=0 not configured means you do not have created a PAGE Object within your TypoScript.
If you copy Data to a new TYPO3 installation, you need to install all Extension that are used in the source-installation. When the extensions are installed, they have to appear in the Template Module.
The INVALID VALUE gridelements_pi1 is the same - it seems you didn't have installed Gridelements to the new TYPO3 Installation.
Install all dependencies and everything should work like expected.
EDIT:
Going a bit deeper - when installed all Extensions, then click on your rootpage (the globe) and then open the templates module. When there is still the No Templates, you need to create one... message, then create a new template for a new page.
After you created it, you can open the tab Includes and select your templates there.
An TYPO3 installation consists of multiple parts:
the TYPO3 source (this can be updated individually)
/typo3_src (normaly a symlink to the TYPO3 sources)
the database (some tables could be truncated (caches))
extensions (all active extensions are needed)
/typo3conf/ext/*
language files
`/typo3conf/l10n'
original data files (in case you want to have images or other data, e.g. pdf)
/fileadmin/ or any other folders you may use with a file-storage record
processed files (images mostly are used resized, which are precaculated and stored for faster access)
/typo3temp/assets, /typo3temp/DATA, /uploads, /fileadmin/__processed__, ...
cached data (some codes are concatenated, so only one file needs to be included instead of a lot of small files)
/typo3temp/var, /typo3temp/CACHE
Not all parts are necessary for a copy of the installation, but it will help if you can copy all parts.
All caches can be rebuild and so there might be some differences like another domain it is highly recommended to delete caches.
Most processed data can be rebuild (as long as the original files are still present). But sometimes it is not recognized that a file needs to be processed again.
In your case I assume you missed to copy the extensions, especially the site extension so that you also miss the definition of your page object.
Related
Static Files in Odoo
I'm new to Odoo, and am working through developing a custom theme for a client. I've worked through the theme tutorial despite the many errors and omissions that exist in that documentation (going to make a pull request to update that after I'm done). My latest struggle is dealing with static files in Odoo, specifically images in the theme.
The Setup
Running Odoo 13.0.20200323 on Ubuntu 18.04 in VirtualBox managed by Vagrant and provisioned with Ansible
The Problem
Changes to image files in the static folder are not reflected on the website. This includes updating the theme in the website theme settings (the update function seems to update everything else). I've changed image names, image content, moved them into other folder, and have not been able to figure out how to have any changes updated on the website. I've restarted the server, doesn't change anything. Updated the theme as stated above, doesn't work. The only way I've been able to have any changes reflected on the front end is to completely destroy and rebuild the server.
Questions
What am I missing? Is there a function I'm not running to trigger Odoo to update what it serves from the static folder?
How does Odoo work with static files in general? On the fly updates to files in the static folder don't seem to have any changes on the front end. Are the files in the static folder copied somewhere else on install, and then served from that other location?
Understanding
I understand that having images and other files change in a folder called static, doesn't make much sense functionally, and that's not my intention for this. Since I'm in development I need to make changes to files, like SCSS, JS, and images, and have those updates reflected on the front end without having to destroy and rebuild the server every time. To be clear, changes to SCSS and JS files that I've registered in .xml files and bundled with various Odoo bundles update just fine when I make changes to them and then update the theme on the backend in the theme management view.
My desire is to understand how Odoo handles the files in the static folder in general, how to update those files properly, and how to manage them while developing and for release.
Answers
I've figured out an answer to the first part of the question as to what I'm doing wrong. It seems like a browser caching issue. When performing a hard reload, empty cache and hard reload, or visiting the site in an incognito window changes are reflected to imagery.
As far as I can tell Odoo is just serving files from the static folder directly. Please correct me if this is not the case.
Follow-up
Does anyone have a good solution for working with changes like this and dealing with browser caching issues?
Answer: I've set up a a couple gulp tasks that use gulp-rev (will replace with gulp-rev-all soon) rev-del and rev-rewrite to handle cache busting through appending hashes to the file names.
I'm going to try setting up Browser-sync in proxy mode to see how that deals with changes to files on reload. I'll report what I find!
Update: Browser-sync has worked well so far as expected. But was kind of useless until I figured out how to work out a fix for the problem below
Does anyone know of how to automate Odoo rebuilding SCSS, JS etc. bundles? So that on file change the theme can be updated and the results seen without having to manually update the theme on the backend to see the results?
Answer: The main task was figuring out how to get live HTML/XML updates working. Which meant building Odoo from the source, and not making any updates or changes to the theme on the backend or frontend from within the Odoo interface. Passing the option --dev xml to Odoo when starting it with odoo-bin allows for the XML code to be evaluated directly, and makes live updates possible. But this extremely helpful (almost necessary) functionality is broken when you make any updates to the them from within Odoo. I'll report on any work arounds to this, but for now as long as I don't touch the theme from within Odoo (update the theme or make edits to it with their editor) then it works great. Also I had to bypass bundling my CSS and JS with their bundler initially to get those updates working live, but may be able to go back and rebundle them now that the code is being evaluated directly.
⭐️Boilerplate and Tutorial Series ⭐️
I'm going to get my whole process for theme building dialed in and then I'll be sharing the boilerplate and build tools on GitHub and also writing and filming a tutorial series on it. Since the built in documentation on that front is straight up error filled, omits critical information and also
I'm trying to build a Visual Studio Installer Setup Project that deploys multiple C# projects and some other files. Included in these other files, there are Access Database with forms that needs updates.
To illustrate the problem, I simplified it :
1- Create a new Access Database file, add a simple form to it with a button and a label and save it.
2- Add the file to the setup project;
3- Set DetectNewerInstalledVersion and RemovePreviousVersion to true
4- Build the project.
5- Run the setup executable.
To that point, everything has worked fine
6- Reopen the Access Database file, add a button or a label to the form, save it.
7- Change the Version number of the Setup project, and at the same time the ProductCode as suggested by VS2015.
8- Rebuild the setup project.
9- Reinstall the software.
Expected: the Access data should have been updated with the new button/label.
What is happening: The file hasn't been updated.
Why is that ? I've seen people talking about the Assembly version number of projects included in a setup project, but that's not my case since I'm not deploying the ouput of a project. I'm simply deploying a file that should have been removed during the uninstall process.
If I do the exact same steps as described before but with a text file in which I add text, it works fine, but for some reason in does not work with an Access Database.
What's wrong ?
If you install a data file, and then run a program that updates it you've added user data to that file, or database. The file overwrite rules don't allow a modified data file to be replaced in the kind of update that VS setups do:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370531(v=vs.85).aspx
Basically it would be a bad idea to ship a product that installs a database that the user updates with potentially large amounts of data, only to have the new version of the product delete the entire database. It's not clear to me how your app deals with updates (do you want that added button/label just to be completely lost, or do you save them in some way?) so recommending a solution is difficult, but maybe you need an uninstall custom action to delete the database, or on an upgrade you add the updates to the existing DB instead of removing it and starting again.
I found a solution. The file wasn't updating because the modified date had changed.
From MSFT site:
Nonversioned Files are User Data—If the Modified date is later than
the Create date for the file on the computer, do not install the file
because user customizations would be deleted. If the Modified and
Create dates are the same, install the file. If the Create date is
later than the Modified date, the file is considered unmodified,
install the file.
Since I had two Access databases (front-end with the forms, backend with the data tables) and needed only one to be updated (the frontend where the forms are), here's the workaround:
1) Change REINSTALLMODE property to amus instead of the default omus. It will force the reinstallation of all files. To do that, I used a PostBuildEvent as explained here.
2) Set the backend file property Permanent to true
3) Add a Launch Condition: Search Target Machineto check if the backend file exists on the computer. Name it something like BACKENDEXISTS
4) Add a Condition value to the backend file in the File System view to install the file only if it hasn't been found by the Launch Condition. In this case, it will be not BACKENDEXISTS. If this is a first install, it will install the file because it hasn't been found. If this is an update, it will find the file because of the Permanent property and will not replace it.
I'm very new to Typo3 and am struggling with a few cached images that refuse to update.
There has to be a option to deactivate all caching somewhere, and to flush everything. I need to know how.
What I have been expecting to find was one button that fixes it all. What I actually found was the following:
The directory /fileadmin/_processed_ contains resized images that the website creates and stores for later reuse, deleting the folder's content prompts the website to recreate everything from scratch, thus reflecting any changes to the original images that are stored elsewhere.
The directory /typo3temp/ runs a similar role like the one mentioned above, it contains semitemporary data from some installed extensions (unlike above not limited to image files). If a particular extension is causing trouble you might find (and empty) it's cache in this directory
/typo3temp/Cache appears to be of interest.
The Install tool accesible from the backend provides a few useful functions, most notably the clear all cache found under the tab important functions.
Furthermore there is a tab clean up which allow clearing cache_imagesizes, cache_md5params, cache_typo3temp_log amongst some other things that don't seem to be of greater interest.
I had the same problem when I switched to TYPO3 6.0
It was caused by the FAL (file abstraction layer).
The only way, displaying a newer verion of the picture was to rename it such like:
oldpicture = _picture
newpicture = oldpicture
I had to copy relevant files from an existing joomla application to a fresh joomla installation. After doing that, some plugins and modules that were working properly on the old installation aren't on the new installation. e.g
I have {chronoforms}Contact_Us{/chronoforms} that is meant to display a contact form, instead if justs echos {chronoforms}Contact_Us{/chronoforms}.
I also have {module _Story_Player} that is meant to display a allvideoshare video but instead just echos {module _Story_Player}
When i access the backend to view these plugins, i get a 500 - An error has occurred with xml missing note, eg, for chronoforms, i get The file chronoforms.xml could not be found although I have all the necessary files copied to the right location.
I have looked through jooomla forums and other resource sites but havent found any pointers so far.
The simplest thing to do would be to re-install the software, as it appears you've missed the relevant configuration files for those plugins (you've probably also missed other files media, language etc).
Chronoforms on JED.
All Video Share on JED
Most good extensions have no problem being installed over an existing or partial installation so you shouldn't encounter any problems.
As #Riccardo Zom, mentions re-installing will also make sure the extensions are properly registered with Joomla! for menus, ACL e.t.c.
What about "Extension Manager" > "Discover" - isn't that supposed to be used in such cases?
I'm trying to deploy a Joomla 1.5 site developed locally. I'm not using the latest version because some extensions that I need are for 1.5 only.
After migrating the database and contents a lot of issues appeared - most of them I believe have to do with Joom!Fish.
Therefore I decided to install a fresh copy of Joomla 1.5 on the targeted server (Yahoo Small Business host), install the template and rebuild the contents.
The problem has to do with the second step: installing the template. I install it using the Extension Manager (without any errors), it shows up in Extension Manager -> Templates, but it doesn't show up in the Template Manager (therefore it can't be enabled). I get the exact same disappointing result when manually FTP-ing the template files. The "jos_templates_menu" table didn't had an entry corresponding to my template; manually adding it didn't had any positive result. I believe that templatedetails.xml is correct.
I've tested other templates (free online ones). Most of them show up in Template Manager.
Odd is the fact that if I try to install my template on a freshly installed Joomla 1.5 site (on localhost), everything is OK.
Can anybody please share some thoughts (from experience or not) with respect to this particular issue? Thanks.
I've had the same issue many times in the past, and can say with near certainty that it roots back to your templatedetails.xml file. Make sure that the names that are being used all match exactly (usually case-sensitive) because Joomla starts by looking at the subfolders found in the Templates folder, and proceeding from there with the templatedetails.xml file that it finds in each.