I have an install of Joomla 2.5.3.
When I create a new article, the default STATUS field is set to "TRASHED".
Now I know that the ARTICLE.XML controls this, however it is not working. It does not matter what I set the default attribute to within the XML, it still remains as TRASHED.
I cannot find where in the code that this is getting generated.
Can anyone shed some light on this?
I've just installed a clean 2.5.3 copy and I cannot reproduce your problem.
I advise you to either:
Reinstall 2.5.3 with a clean copy from here (the same I used).
Update to the newest 2.5 version (currently 2.5.8) which can be downloaded here.
If in either case you want to preserve your content, you can use Akeeba Backup.
Related
I have CKEDITOR inline embedded in my portal but I am unable to find the version of CKEDITOR.
CKEDITOR.version returns %VERSION%
The changes.md file doesn't exist either.
If CKEDITOR.version is set to %VERSION% it means that you're using a development version of CKEditor, not a release (or that it was built incorrectly). Lack of changelog means that someone removed it... Not a very fortunate move as well. So if you don't know its source and its not a clone of CKEditor repository it will be very hard to guess what version it is. You can try to check CKEDITOR.revision and compare it with http://github.com/ckeditor/ckeditor-dev. But if that fails too, then the only solution will be to compare code manually.
I've tried every method I can think of to update from 3.1.5 to 3.2.3 and each time it pretty much kills my site and leaves me with the error:
Fatal error: Call to undefined method JLoader::registerAlias() in /homepages/.../libraries/cms.php on line 61
At which point I just clobber the rest of the site and reinstall my backup (oh man you GOTTA LOVE Akeeba).
I've upgraded Joomla successfully and unsuccessfully about 100 times over the past few years on various sites and this is the first time I'm stumped as how to move forward.
One interesting piece of data is in the Admin Control Panel of the 3.1.5 is that the Joomla version says "Unknown" even though the System Information lists it as 3.1.5.
So, anyway, what is the ABSOLUTE, BLESSED method for moving from 3.1.5 to 3.2.3? If I should simply be able to install the 3.2.3 upgrade zip file then I guess I'm toast. In that case, what would happen if I left the database as is and cleared out all the files and then installed the 3.2.3 full stable package? Would that work?
Do you have Akeeba backup installed? You need to make sure it is updated first before updating joomla.
So if yo have a back up, restore that, update Akeeba, then update Joomla again.
http://www.rockettheme.com/forum/general-discussion/215394-pressing-the-joomla-update-button-killed-my-site
The solution was pretty easy, though unexpected. See here.
I have just (finally) started using sublime text 2, and I am liking it so far (apart from lack of intellisense / autocompletion :(, though tried codeintel but its not what I expected), I am moving from netbeans (can't afford to use it because of memory eating nature :(). Anyway My current issue is I don't know how I can use latest update of sublime text 2 (portable on windows), it kept prompting me about update and once I listened to it and it downloaded new version but there was no step involved in actually updating the existing version to new one instead I have another portable version with newer files, and my issue is i have install several plugins in the old version and I don't know how I can use those in this new version :(.
Note: It just started saying me this version has expired so thats why I am seeking help so I can use new version but with my already installed plugins (emmet, js minifier etc etc :().
I have googled alot but found no windows based guide which helps me solve my issue :(.
Thanks in advance.
Assume that your old version is installed in Sublime.old, and the new version in Sublime.new. Make sure Sublime Text 2 is closed, then move the Sublime.new\Data folder to someplace else (like your Desktop, for now), just in case anything breaks. Then, copy (don't move) the Sublime.old\Data folder to Sublime.new. Fire up the program and check to see that everything is there, and works properly. Please note that this method will not work when upgrading from ST2 to ST3, as there are major differences in the way plugins are run.
I have this posted here:
https://getsatisfaction.com/pixelandtonic/topics/wygwam_not_styled_in_cp_entry_and_not_functioning_shown_errors_attached
...but I really need a fix asap if anyone can help here.
I can't get Wygwam to work.
It started with me running this:
EE 1.6.8 (Again, can't update)
Wygwam 2.1.6
FieldFrames 1.4.5
I wasn't able to activate the module. I would receive errors and then the field was jacked.
I then upgraded Wygwam to 2.6.3 and that allowed my to enable the module.
The problem I have now is this:
When I try to Add a new Wygwam field, it tells me that there are no configurations available. When I go to 'Edit Configurations', I only get the serial number input field. I added the serial number, but nothing changed. Under 'Editor Configurations' it just says: There are currently no configurations.
Now I have the existing fields back, however, I cannot view source and do not have any "Configurable Editors" available. I also cannot setup any "Configurable Editors" in the module because I have no settings/options display. Also, I cannot add any new Wygwam fields because when I do, I just get a white screen.
Ok, While this may not be the best answer to provide, it has provided a resolve to the situation I was in.
First off, Kudos goes to Brad Bell at Pixel & Tonic for sticking with me via emails in trying to get this fixed. I am in a situation with this site in which I can't provide access to the site, files, data, etc. It definitely makes getting help with EE related instances more difficult. Brandon and his staff definitely know how to push through these issues.
Thanks guys.
Nothing we were trying was working. What I had to end up doing was rolling back the versions of Wygwam and Matrix from the more recent releases that were installed to WW 2.1.1 and Matrix 2.0.11
I didn't try newer versions as I want to push harder than ever now for a site update/rebuild due to these issues and others. The site is again functional in these areas and they can move forward, (or laterally... depending on your stance), again.
Am looking to upgrade Mangeto from version 1.1.8 to version 1.5.
This is a quite a leap I am taking I know, but and I have tried the following already (as some one else had suggested on another site):
dump v1.1.8 database, restore it in a new database.
install magento 1.5 pointing on the restored v1.1.8 database
let the upgrader run
add the old theme files
test that it all works.
When doing that, the upgrader kept saying some tables already existed.
Can anyone help me out?
Thanks
It's fine now, basically make sure you're using the same server environment.