i am trying to use live writer of scribfire in my joomla 1.7.3
neither solution detects automatically.
i have installed the joomler.net solution.
enabled all plugins.
api adress i put in is:
Enabled SEF
http://yoursite.com/component/xmlrpc/
Disabled SEF
http://yousite.com/index.php?option=com_xmlrpc
and i installed the library recommended:
still nothing works....
does anybody knows how to solve this?
i have RS firewall installed but even when disabled nothing works...
i will appreciate any suggestion.
live writer solution:
make sure ACL is configured to Allow for the user (second field only) and not inherited.
also while live writer is communicating with the joomla press save on the component options.
it works!.
scribfire was configured secondly so mabye the first solution helped.
the right API location is:
yourdomain.xxx/component/xmlrpc/
have fun.
Related
I am trying to upgrade Joomla from 2.5 to 3 but update button is not showing on administrator panel. It is showing “Joomla! is up-to-date”. How will I get update button. Following errors came when I try to troubleshoot.
I am not able to get response from update.joomla.org. Is it due to proxy applied on my connection. If yes then could you please let me know the step to overcome this issue.
When I get in touch to our technical support team then they provide me proxy URL with port number. Without any credential. And they told me that I have to surpass this URL after using the proxy URL. But I am not sure how I can use this proxy to get response. Please suggest and let me know the solution. Thank you!!
Errors :
Update: :Collection: Could not open http:///update.joomla.org/core/sts/list_sts.xml ;
Update: :Collection: Could not open http:///update.joomla.org/core/jed/list.xml
Within the administrator area navigate to the 'Joomla! Updater' component (under Components) - when there click on the 'Options' button in the top right of the screen. When the pop-up appears, change the 'Update server' to 'Short Term Support' and click the 'Save & Close' button within the pop-up. Once closed, the updater component should go off and check for the latest version on the 'Short Term Support' branch. The text that said 'Joomla is up to date' should be replaced with the option to install the 3.5.1 version.
Make sure you take a backup before updating. Your template and other extensions may not be compatible with the 3.5.x branch so it's best to either make sure that they are compatible or find an alternative solution.
For others that might have been scouring the internet to solve this problem, I had the same thing happening to me on a very old site that needed to be upgraded. I had an early 2.5 site which I managed to update to 2.5.28, but could not get any further due to these errors.
Most posts on this that you'll find will refer to the https version of the error, but in my case I had the same problem is the OP, where the file that could not be opened was on the http URL.
Trying to directly load the http site seemed to work, until I noticed that my browser was automatically redirecting to the https site. I don't know if that was the browser, or a server redirect causing this, but it let me to another solution to this problem, which is that these resources obviously are no longer hosted on an insecure site.
Open up the administrator/components/com_joomlaupdate/models/default.php file and around lines 37-47, modify the listed URLs from http to https. Then rerun the purge/udpate check cycle and you should now get the update found.
In addition to this, other sites that are listed as not being found on http links can be updated by modifying records in the #__update_sites table. YMMV with these, as most of them are going to be 3rd party sites that may/may not have changed hosting. In my case, most of them had just disappeared. Notably, the core update site is listed in this table, but it gets overwritten by the aforementioned script, so updating the DB doesn't help.
I have a huge problem with my VirtueMart. I try to develop a new payment module for it. The main problem is that no matter how I do it VirtueMart seems to refuse to let me store the plug-in in the database and also it refuses to let me choose it as a payment method.
I have disabled all other "countries" except the one that the module is written for. I have followed all guides on joomla mastery. I am convinced that my constructor is correct according to the scarce documentation I have found. I have even copy/pasted an existing payment module and changed all names for the database to something different so I can see if it's created and it's a no-go.
I am starting to get desperate. Does anyone have a good virtuemart developer guide? Do I need to turn some flags on (the flag to update/write to database is on in joomla and virtuemart) or off? How can I programatically FORCE VirtueMart to actually listen to what it say should work in all documentations I've found?
I am trying to figure out why the tinyMCE WYSIWYG editor in the CMS module of Magento will not upload images. I can create/delete folders but any file will simply not get uploaded, and there seems to be no message as to why the file is not successfully written on the server.
Anyone may have an idea why?
** Update **
I'm using Magento 1.6.2. I have tried to track down the problem and it seems that the controller never gets executed. I have added a line to log the arguments in the uploadAction() action (in Mage_Adminhtml_Cms_Wysiwyg_ImagesController) and nothing gets logged.
This is project inherited from someone else, and was modified to some extend, but nothing seems to point out that this part of Magento would have been touched in anyway by the modifications.
** EDIT**
The project associated with this question has been dropped and I no longer can provide an answer to this question. If anyone can confirm a working answer (as this problem was apparantly common with Magento), I will gladly mark that answer as "accepted".
Otherwise, I will flag this question for removal for the aformentioned reasons.
Thank you.
Other than solutions provided here, it may occur when you use a CDN (or a different domain) for your javascript and media files in admin panel. If you use CDN, use it for your website(s) scope and use your own domain for default scope. It will make your website(s) media and javascript files to be loaded from CDN, and backend's media and javascript files to be loaded from your own domain. This will solve your problem.
There are some known issues with flash image uploader on Magento. Unfortunately when it falls, it falls silently. Here are some cases when smth can break it:
if you try to use it with secured connection using open ssl certificate
if you're using it on server with apache authentication
on some Magento versions with prototype 1.7
I think the latter is your best bet. Maybe you should try to apply the patch from here: http://www.magentocommerce.com/boards/viewthread/4348/P45/#t327010
In my case it was a cross domain problem, and one quite hard to find if you ask me...
What was puzzling me was that the uploader for product images was working like a charm but the one in the CMS section was failing completely silently. We are serving the skin folder from an Amazon S3 bucket, and the flash uploader lives under that folder.
Interestingly enough, our version of Magento (1.7.0.2) is using two different methods to calculate the path to the SWF file, depending whether you are under CMS or Product update.
The CMS file (app/design/adminhtml/default/default/template/cms/browser/content/uploader.phtml) is using the following method to embed the Flash Uploader:
<?php echo $this->getSkinUrl('media/uploader.swf') ?>
While the Product image uploader is using:
<?php echo $this->getUploaderUrl('media/uploader.swf') ?>
In our case, the first one resolves to the AWS S3 url, obviously in a separate domain, while the second one will still reference the local domain's url.
So yeah, the quick, dirty fix would be to replace getSkinUrl for getUploaderUrl in app/design/adminhtml/default/default/template/cms/browser/content/uploader.phtml. Alternatively you can extend the core to load a different template in which you would have replaced that method.
I hope this helps somebody... I wish I had found something like this five days ago when I first stumbled upon the issue :-)
Are you using flash uploader with https? If so, is your secure address in differente domain (usually used in shareds ssl)?
I got some trouble with this. I solved by installing a flash uploader disabler plugin.
You can download the plugin with this downloader key:
http://connect20.magentocommerce.com/community/Dull_Uploader
I hope it helps.
I am currently running Joomla 1.5, I have moved my site to a new domain and thought I had foloowed the procedure correctly. But now my menus are gone and it seems like articles are not showing up in their proper modules. Other than that the components i was using are now giving me a 404 component not found error. Does anyone know why this is or how I can fix this? Please I really need some help or direction....
Thanks
Here is my link: http://davidjamesmedia.ca
Make sure you check the following things:
Ensure you made the correct database setting changes in the configuration.php
Ensure you server is running PHP 5.2+
Make sure your MySQL version is arounf 5.0+ but also not too high such as 5.5.24 this can cause some problems with depreciated functions.
Also make sure your server has Apache mod_rewrite extension installed if you were using SEF before else you can turn SEF off in the configuration.php
For some reason, when I log into my joomla 1.6 backend, it is now empty, displaying only a logout button. Any Ideas?
I just went through the same problem but on J!1.7.3. There may be many, many reasons but please check using just URL if you can see for example:
[YourDomainHere]/administrator/index.php?option=com_content or
[YourDomainHere]/administrator/index.php?option=com_modules
If content is listing and you're missing just Admin-menu and sub-navigation in back-end --> this means you messed-up with access levels and viewing access.
If you can't see content listing - ignore the rest of this post :-)
...with access levels and viewing access. To check that, try entering [YourDomainHere]/administrator/index.php?option=com_users&view=levels and enter each position in the list. Joomla backend navigation module usually has Access set to Special, so focus on this one. When enter Special - manager, author and super administrator should be ticked. If everything empty in any from the list - this is your issue :)
You need to add manager, author and super administrator to your Special access level. Obviously you can't see Save button, so you need to use database. [wrrr :) sounds scary?] Not a big deal, just go there using for example phpMyAdmin and find _viewlevels table. In there just edit Special and add [6,2,8] values to set up manager, author, super.....
Update database. Try to log-in one more time (close browser and clean cache before).
I hope if this wasn't helpful for you, will be for somebody else.
p.s. There may be a way of 'saving' changes in you joomla access levels with URL. Then you don't need to go to DB .. but I don't know if this is feasible at all :)
Check the rewrite of htaccess and the $mosConfig_absolute_path variable in config.php
Apparently, the Bluestork Template (admin template) has some security issues. In my case there were some missing files in the template folder /administrator/templates/bluestork/ that caused the administrator screen to appear blank. I've copied a clean version of the template in the bluestork folder and after that I was able to see the backend admin area.
I've removed the bluestork templates entirely for now, which seems to be the best option. Joomla installs 2.5.8, 2.5.6, 2.5.2, 1.7.0, 1.6.3 are affected. The Blustork Template is a target for hacks with old Joomla.
this happening becoz of admin user lost his permissions. see below article to fix this issue
http://www.codentalk.com/joomla-admin-showing-blank-page/