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?
Related
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.
I am looking for an extension to my joomla site where users can download pdf instruction sheets, forms, etc from a list of files available. I would must rather it forced them to log into the site to be able to download but I can adjust that by just making the module accessible to registered people only. So that is not a must have.
Anyone knows of any extension like this one? I know JoomlaShine has this extension in their JSN CUBE template but they don't offer it by itself.
Akeeba Release System (ARS on JED) is probably the best solution of it's kind and is free to download, we use it on several of ours and our client sites.
You can also combine it with the Akeeba Subscriptions (AkSubs on JED) system to manage site access including integrated access to file downloads.
Of course there are lots of document download extensions on the the Joomla Extension Directory.
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.
Can I create a symlink to the local extension from aonther project folder? I have a common local-server and i need to implement same extension on all local project-installations. I tried to put the symlink, but some times i do not get expected output. I get it only after clearing the cache of that perticular project.
Your scenario is a common one I guess. But as Omar said, linking to the same code base of the extension through several typo3 instances is not a good practice.
But we have the same structure as yours, we realize this through SVN. All of our projects got a SVN repository and common extensions have their own repository. Through svn:externals the extensions are linked into the concrete project. This has the advantage that you can change the extension in the concrete project and after committing all other projects (that do have to update from svn though) contribute from it. I Think this would fit your needs, too.
If I understand your question correctly you have several Typo3 sites on the same server and want to share an extension between them using a symlink. I don't think that is a very great idea because many extensions use tables and every site normally has it's own database so you would have to do a lot of tinkering to get that to work.
Instead you could make all the modifications to the extension files in the typo3conf/ext/extension_name folder and then export the extension to a t3x file (Ext Manager in the Backend). This t3x file can be installed as a extension (Import extension) on all your other sites.
If you extension does not use a database and you are planning to make frequent changes then I guess you should be able to make that work (the symlink). Otherwise I recommend you use the first approach I described.
I have not tried this, but you should be able to install extensions globally in Typo3. What this means is that the given extension is placed inside '(typo3_src/)typo3/ext/' instead of 'typo3conf/ext/', presuming both sites use the same Typo3 Core/Source (and thus typo3_src is a symlink to the location of the core).
You can enable installing global extensions via the Install Tool. Once inside the tool, click on 'All Configuration', then search for allowGlobalInstall. Or put the following line into your localconf.php:
$TYPO3_CONF_VARS['EXT']['allowGlobalInstall'] = '1';
At last, but not least, you need to make sure the 'typo3/ext/' directory is writeable.
Hope this will be to some help. If you have any further questions, let me know :)
As Björn mentioned, I'd sugegst to install them globally. Mind you, updating the source will require to move the extensions accordingly..
As for "expected output": be aware that the code in these folders is cached in various ways (mainly page content and config settings), and hence not always run. This is the reason a change done from "outside" the current installation is likely not to propagate to your output without clearing these caches (as you have observed).
When you actually install an extension via the extension manager, the cache should (if correctly configured) be cleared (interested parties may search for clearCacheOnLoad in class.em_index.php to reveal a clear_cacheCmd('all')). There is a small checkbox, which is normally checked, during the installation process to accomplish this.
Omar's first approach is therefore, as I see it, the more easy way to get "expected output" and less jumbling around with global extensions.
Previously I was able to download extensions without a problem. Now when I click on admin > system > magento connect > magento connect manager
I get a blank screen with a few characters:
http://skitch.com/a1anm/ntb31/http-127.0.0.1-8888-thefix-index.php-adminalan-extensions-local-index-key-9318fe8596ce8bec19757cc8ef4d8447
I am able to access the downloader via mysite.com/downloader. The problem is evertime I download an extension now and then try to access admin > system > config I get the same blank screen error. If I uninstall the last extension it starts working again.
I’ve tried a number of different extensions but get the same problems. I also tried disabling all current extensions and it didn’t dix this.
Anyone know how I could fix this? Or is it possible to reinstall the downloader without reinstalling my entire store?
I'm still a novice with Magento, but did some research on your problem that you may find helpful.
It looks like this thread over at the official Magento forums has some good suggestions:
http://www.magentocommerce.com/boards/viewthread/31791/
It may be your problem is caused by either permissions problems on your filesystem, or a corrupt core extension.
I would say that if you can't resolve your problem based on any of the advice in that thread, your best bet would be to uncomment:
ini_set('display_errors', 1);
in your magento/index.php file and post here any error messages you get when trying to access Magento Connect.
Good luck!
It looks to me that your index.php file (or some other involved file) has a byte order mark (BOM) at the top of it. Try using an encoding converter to take out the BOM.