I've just updated to Typo3 4.7.0 and most of my projects gets a call to undefined error in t3lib_div::view_array? What happens to the function view_array?
It's Deprecated since TYPO3 4.5 - Use t3lib_utility_Debug::viewArray instead
As you can also see it's removed from 4.7 (that's normal in TYPO3 that methods are removed in two versions after they were marked as deprecated)
Related
I need to update my TYPO3 4 to 4.5.
I installed 4.5 and symlinked to the new source. The problem is that I can't get into TYPO3 4.5 install tool using localhost/typo3/install. It shows "page isn't working".
How do I get into TYPO3 4.5 install tool?
Page isn't working is a default error message when a site returns a 500 error. You'll need to check your error log to see whet the error actually is.
Also TYPO3 4.5 is old, not maintained anymore and not secure. You should not use it. Please update to at least 7.6.
In the folder typo3conf are some files like:
temp_CACHED_ps12c3_ext_localconf.php
temp_CACHED_ps12c3_ext_tables.php
The bold part might probably different but those files you can delete and then try again.
Also make sure that you meet the requirements concerning PHP-version and MySQL-version.
The deleted files will be created new, so you aren't deleting unique information, but the new files differ a bit.
The main issue can be the PHP version. I am running Typo3 4.5 successfully on PHP 5.3. However it will not run on higher PHP version. However, if the update is done on the same server, then PHP version issue might not be applicable.
The exact error detail will come up in the PHP error_log. Make sure that error logging is enabled in the PHP.ini setting.
What are the steps to downgrade a typo3 site and is this even possible?
I cannot get a few plugins to work on my 7.4 typo site so I decided to downgrade but I cannot find anything about it on typo forums or in the documentation. Are there any steps I can follow if this is possible.
Before upgrading your website you should always backup your data and avoid downgrading at any time.
Compatibility mode for TYPO3 6.x
The system extension compatibility6 is shipped with TYPO3 7, have you tried installing this extension already?
See also: Retaining compatibility to TYPO3 CMS 6
Downgrading from 7.x back to 6.2
There is no such thing as a documentation with downgrade instructions. But if you have no other option than you can try the following:
Before running TYPO3 again:
Backup your data
Remove the TYPO3 7 core as well the composer.json (and /vendor/ directory), .htaccess and index.php file from your website.
Remove the content of /typo3temp/, /fileadmin/_processed/ and /fileadmin/_temp_/.
uninstall all TYPO3 7 related (system) extensions by setting the state to inactive in the /typo3conf/PackagesStates.php file.
Uninstall or downgrade all extensions which are only compatible with TYPO3 7.x.
Set manual the ['SYS']['compat_version'] in /typo3conf/LocalConfiguration.php to '6.0' (we let TYPO3 think that we are uograding from 6.0. Please note that TYPO3 7 doesn't have this option anymore and you need to create it yourself.
Remove all array items from the array ['INSTALL']['wizardDone'] in /typo3conf/PackagesStates.php.
Set manual options such as ['FE']['activateContentAdapter'] back if needed.
Put the TYPO3 6.2 core back in it's place.
Now you're allowed to run TYPO3 again:
Log in on the install tool by accessing /typo3/install/.
Run the database compare but please don't remove fields or tables that belongs to extensions which you have temporary disabled for downgrading purposes.
Clear all caches from the install tool.
Run al steps from the upgrade wizard.
Reactivate disabled extensions (manually).
Check if the ['SYS']['compat_version'] is set to '6.2'.
Test your TYPO3 instance as good as you can.
Arek van Schaijk solution worked to downgrade 8.7 to 7.6. But a couple of additional changes might require.
in the file
typo3/sysext/core/Configuration/DefaultConfiguration.php
change fileCreateMask from 0664 to 0660
change folderCreateMask from 2775 to 2770
Symbolic links can be rectified with this solution.
Hi since I moved my Typo3 to another Webserver I get this error on my frontend.
Typo3 Developer API error:
The function
fe_renderTemplate
reported an error. Please check the arguments you passed to that
function in order to solve the problem.
Someone knows that problem?
My Typo version is 4.3.8
Greetings
First of all, you should not use TYPO3 4.3 anymore because it's way outdated. If you can't upgrade quickly, please use at least the latest 4.3 version which is 4.3.14. After 4.3.8 there were 3 security releases so your installation might be insecure.
I suspect that the problem is that your new server is running a never PHP version. Your error comes from an extension called "api_macmade". Are you using the latest version of this extension? Do you still need it?
If you still need it and you are already using the latest version, please post the function of this method in your post so we can help you fix the problem.
After updating my TYPO3 CMS from 4.3 to 4.5 LTS the news were no longer displayed. So i decided to update tt_news extension as well. It was at version 2.5.2 and had to be upgraded to the newest 3.4.0. It suggested to me, to use its own 'update script' (and as mentioned at other resources too) to work properly because of serious changes. Under 'Extentension Manager' - 'tt_news' - 'UPDATE!' it shows up with a simple blank page and nothing can be done.
Is there any hint to solve this?
You have got some PHP error. Copy the /var/log/apache2/error.log or enable in TYPO3 Install Tool configuration PHP errors.
Does anybody have successfully working module in DNN 6 with the Ajax Control Toolkit?
My modules stopped working when we migrated from DNN 5.x to to 6.x.
Modules compile without errors but I am getting client side script error:
'AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the ToolkitScriptManager in AjaxControlToolkit.dll'
Seems like this is conflict with Telerik's controls, according to information that I have found. But I didn't find any info how to fix it.
You should be able to use older versions of the ASP.NET AJAX Control Toolkit, but once they start requiring the ToolkitScriptManager, you're out of luck with DNN (though you'll be out of luck with any version of DNN, since there's not a way to override the type of ScriptManager it uses.
Starting with DNN 6, they use Telerik's RadScriptManager. Previously, you could modify the core code to switch out for the ToolkitScriptManager, but now switching out might cause other issues.
It could work together, but you'll need do some modifications to the core of DNN.
Here the list of things to do:
Check that you're using latest version of .Net 4.0 binaries of AjaxControlToolkit (I was able to let it work for DNN 6.0.1 with Telerik 2011.01.519 and ACT September 2011 v4.1.50927)
Check that in your web.config you have assembly binding redirects for System.Web.Extensions and System.Web.Extensions.Design to the version 4.0
Take DNN source package, find Library\Framework\AJAX.cs, locate method AddScriptManager, instantiation of RadScriptManager in it, for the version 6.0.1 look into line 54. Add one more property initializer:
EnableScriptCombine = false. Compile it (in Release configuration, of course), take DotNetNuke.dll and drop into your DNN installation.
You should be done.
Credits goes to Telerik support, despite it's stated there that it should work out of the box starting from 2010.1.625. Not sure, did I get them wrong, or they just reintroduced this bug.
P.S. DNN support promises to release version 6.1.0 in November with updated Telerik controls, which should fix this issue, at least on their opinion.
Just checked with nuke 6.1 and the last version of jaxcontroltoolkit - still the same error.
It looks like it's not supported anymore. Sad:(