I'm developing component in Joomla 3.2 and having problem with saving configuration values to extension table.I've included the configuration values in config.xml.After installing my component,i would go to my configuration page and clicked save.It has updated successfully in extension table's params field for my extension.But when i installing component the configuration values should be update in extension table.Can you please help to solve this ?
Related
I have a "SOURCE" module in laravel project. The edit functionality was working fine before I changed the DB. I added a column in DB table "source". After adding it, whenever I try to edit the source data from admin panel, the data gets modified but shows the error: simplexml_load_string(): Entity: line 1: parser error : StartTag: invalid element name
I am using API's in my project where I have used the function simplexml_load_string(). But this was working fine before I added a column to the DB. What could be a possible reason and solution for it?
I figured out the issue. The issue was with my apache server version. To resolve the issue with the CURL extension of PHP, I installed Apache AddOn (Version - 2.4.28) to support PHP (>7.2) extensions. I downloaded the same from here - https://wampserver.aviatechno.net/ and install it at my end. Restart the Wamp Services and choose the updated version of Apache web server. And it was resolved.
Magento 1.9.3 - I created a custom module for add attributes in customer account.
Since last one year I am upgrading using same module but now when I am trying to upgrade mysql4-upgrade-0.1.9-0.2.0.php it's not working.
core_resource database version is 0.1.9
Cache i have already cleared
Same upgrade script is working on development server
Issue has been resolved. Due to the cache problem new version was not updating but after clear cache multiple times it's working.
Im getting an error that i have now idea hove to solve.
Im getting this error after saving a slider images for my joomla page:
RecursiveDirectoryIterator::__construct(C:\xampp\htdocs\bondenssliderDSimagesDS,C:\xampp\htdocs\bondenssliderDSimagesDS):
How do i solve this?
It's look like you have a problem with "DS constant". As per Joomla documentation DS(directory Separator) constant has been removed from version 3.x. If you are using any custom component which uses "DS" then it will generate error as it's not defined in the library. To resolve this issue either you can tried to define :
if(!defined('DS')) define('DS', DIRECTORY_SEPARATOR);
added to main .php file of components/plugin or module.
Or you can directly install following plugin:
http://extensions.joomla.org/extensions/extension/core-enhancements/performance/ds-constant
I have create a custom module at admin ,in my local machine it is working fine but at server it is not loading and even not showing header and footer as well,It is only showing logo and logged user,
Cannot debug how to resolve this issue.
My machine and server configuration is same,Please advice me for resolving this.I am using Magento 1.8 .
Remove the comment from [magento-root]/index.php
ini_set('display_errors', 1);
Also enable logs(Admin> System> Developer> Log Settings) and check the error in [root]/var/log
Make sure to:
Clear your cache
Create the corresponding module configuration file in app/etc/modules/Your_Extension.xml
I have been upgrading a joomla (2.5- to - 3.1) site locally but the upgrade is broken. The sql upgrade did not pass. I have been trying to use the database fix option but even like that did not get it to work in my case.
Database schema version (2.5.11) does not match CMS version (3.1.1).
Table '#__content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.3-2011-10-15.sql.)
I have been trying to execute manually the other query but fails.
How could I fix my broken tables?
Where could I get a valid sql upgrade script?
Try clicking the "Fix" button on the Extension Manager > Database view. If this still does not resolve your issue, you'll need to manually apply all of the fixes. You can grab the SQL updates from GitHub (the same relative file path applies as well) and manually run each file's queries using a tool such as phpMyAdmin. Note you'll need to change the table prefix (#__) to match that of your own site.
had the same problem when doing upgrade 2.5.11 => 3.1.1, fixed it by first using phpmyadmin to add a title_alias field with VARCHAR(50) to #__contents table.
after which joomla added another complaint that title_alias should not exist in 3.0.
After applying 'Fix' I guess the old update scripts for 1.7 first changed title_alias to VARCHAR(255), then the update for 3.0 removed it again, updated the schema version in the db
and joomla stopped complaining...
Hope this helps you.