i have installed a plugin in Moodle that is ment to translate textstrings into different (installed) languages.
The installation did work, registering with Google-Cloud and getting an API-Key did work as well. In the (over)load of information on how to use the google service i found some settings that i adjusted.
But . . . i still get an 403 authorisation error.
The google console shows the attempts to get translations but none is made.
Anyone an idea where i should search for a solution?
Regards,
Jan
The plugin link says it's been superseded
"Content translation filter (superseded)"
https://moodle.org/plugins/filter_fulltranslate
Have you tried the new version?
https://moodle.org/plugins/filter_translations
Related
I have a server that hosts several WordPress sites. I use wpcli to update plugins in all of the sites, both manually and with a bash script.
One site has just started throwing an error:
Error: Callable "Queue_Command" does not exist, and cannot be registered as `wp queue`.
I have searched and found nothing at all that matches this error. Can anyone here explain what is causing it?
The site in question is running Wordpress 4.9.5 and WooCommerce 3.3.5, in case that is relevant.
RESOLVED - the new Mailchimp for Woocommerce version 2.1.7 has this issue fixed
So far it seems like the issue is caused by Mailchimp for Woocommerce plugin. https://wordpress.org/support/topic/cron-error-10/
Check if you have that plugin installed and see if removing/disabling it resolves the issue. After that we should check with the plugin developers if they can fix the actual cause of this.
I'm having difficulty in integrating AEM 5.6.1 with Site Catalyst. It allows me to connect in the configuration successfully, but does not work on the framework setup.
I've followed the standard procedure to connect AEM to SC and it accepts my login in the configuration, but fails on the framework set up with the browser message 'We were not able to login to SiteCatalyst. Please check your credentials and try again.'. Behind the scenes in the server log;
12.12.2014 14:10:06.967 *WARN* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.SitecatalystHttpClientImpl Data center 'https://api3.omniture.com/admin/1.3/rest/' responded with errors {"error":{"code":500,"message":"Internal Server Error"}}
12.12.2014 14:10:06.967 *ERROR* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.servlets.SitecatalystServlet Call to SiteCatalyst method 'Company.GetReportSuites' failed com.day.cq.analytics.sitecatalyst.SitecatalystException: not authenticated
I've tried accessing via the API Explorer and it works.
I've tried the troubleshooting guide without success.
I can log in to Site Catalyst, I'm an admin, I am in the web services access group.
I've tried using a clean install of CQ5.6.1 with geometrixx - it doesn't work either.
I've tried this from a server and from a localhost/dev machine with the same results. No proxy. I've even tried using the shared secret as the password but then it doesn't connect at all, and fails on the configuration screen.
What might cause this to fail?
If it doesn't work with a fresh install and Geometrixx, then it's probably an Adobe bug. That's typically the first thing support will ask you about.
I would also verify using Geometrixx Outdoors, or a more recent demo site, on your fresh install, just to ensure it's not an outdated ClientLib issue.
I know this isn't a direct answer to your question, but honestly, I would approach the integration differently. I've worked with the AEM-SC framework and it's buggy at best. It's very finicky, it doesn't REALLY work the way the documentation claims, and it requires that you're very specific about what Clientlibs are on the page.
Moving forward, I think using Adobe Dynamic Tag Manager is the better approach, for many reasons. My understanding is that it's Adobe's recommendation as well. I'd consider moving to that. In AEM 5.6.1, you'll have to customize your integration with DTM, but it's not very hard.
Solution: Add a property on the configuration node for sitecatalyst: (eg. /etc/cloudservices/sitecatalyst/my-sc-configuration)
server=https://api.omniture.com/admin/1.2/rest/
it also seems to work with newer API versions such as https://api3.omniture.com/admin/1.3/rest/
It would appear that for 5.6.1 it ignores the OSGi configuration, at least for the configuration screens. With this extra property, the framework page loads without error and allows selection of the RSID.
The Google Earth browser plugin apparently no longer requires a key and it's impossible to request one.
The problem is when I run their sample code (Chrome 18 and FireFox 10) found here I get an error message:
The Google Maps API key used on this web site was registered for a different web site. The developer of this web site can generate a new key here.
When I check their plugin page it tells me:
Good news, you already have the Google Earth Plug-in installed. (Version 6.0.3.2197)
So no key is required, but when I try to run the code sans key I'm told to get one, and I can't because Google has removed the ability to request one or download the update. I read online that 6.2 is the newest version but the key has not been required since 6.
Any advice is appreciated.
After trying a force refresh, emptying the cache, and upgrading the browser, Google Chrome still wouldn't allow my example that doesn't use a key to work. I've figured out how to fix the issue.
The problem was that Chrome wasn't automatically updating the Google Earth browser plugin, regardless of the browser. Additionally, their plugin page confirmed I had an old version (6.0.3) but wouldn't allow me to manually update either. So I deinstalled the plugin following these instructions, and then downloaded the newest version (6.2.2) and installed it. One final thing I had to do (on my MacBook Pro): the new plugin installed in Library in my user directory
~/Library/Internet Plug-Ins/
but to get it working correctly I had to move the "Google Earth Web Plug-in" file to the root's library and then restart Chrome.
/Library/Internet Plug-Ins/
The Earth API doesn't require a key - your sample code appears to be working properly. In case you do see an error message in the future, make sure that there's no key= parameter when loading the Google JS:
<script src="http://www.google.com/jsapi?key=ABQIAAAAwbkbZLyhsmTCWXbTcjbgbRSzHs7K5SvaUdm8ua-Xxy_-2dYwMxQMhnagaawFo7L1FE1-amhuQxIlXw"></script>
The keys are specific to a domain, so if you copy old sample code from somewhere (such as from the Demo Gallery, for example) you should just strip out the key=xxx portion:
<script src="http://www.google.com/jsapi"></script>
Despite it saying you don´t need an API key for Google Earth at various official places, your problem is solved, if you create one on https://code.google.com/apis/console (under "API access" and then click on "Create new browser key") and include in the jsapi include: <script src="//www.google.com/jsapi?key=yourkeyhere" type="text/javascript"></script>
We have been using the Grails Facebook-graph plugin for a while now - it has been working perfectly until earlier this month when FB apparently turned off their old authentication scheme, and indirectly forced everybody to use oauth2 instead.
This post from FB https://developers.facebook.com/blog/post/525/ describes the changes, and the issue in the Grails plugin seems to be that it does not comply with the new standard.
The main issue appears to be in the way the active user data is being maintained in the plugin. This is currently based on the FB provided cookie "fbs", which contains all the necessary session data related to the active user. Unfortunately, this is no longer provided by FB (apparently replaced by a "fbsr" cookie instead).
I have searched the FB documentation, and in various forums for details on how to upgrade the plugin, but unfortunately without luck.
Can anyone help with a hint or two on what steps should be performed in order to get the plugin updated?
EDIT: I think the updated version of the plugin (0.14) has been pushed the public repository. You should try grabbing that one first before reading the rest of my answer.
It looks like the plugin maintainer, Jesus Lanchas, made some updates over the last few days to enable oauth2 support. It has not been pushed to the plugin repository yet, but I was able to get it working with my project. Here's what I did:
#Install a local copy of the plugin WITHIN my project
mkdir plugins-local
cd plugins-local
git clone git://github.com/chechu/grails-facebook-graph.git
mv grails-facebook-graph facebook-graph
Update BuildConfig.groovy and tell grails where to load the plugin from. I put this line before grails.project.dependency.resolution
grails.plugin.location.'facebook-graph' = "plugins-local/facebook-graph"
Uninstall the existing facebook-graph plugin from my project
grails uninstall-plugin facebook graph
This is a temporary solution for me until the offical update hits the repo, but it allows me to make sure I'm using the same new code everywhere.
EDIT: we released our Facebook Grails SDK on GitHub :
https://github.com/benorama/facebook-grails-sdk.
Currently only tested on Grails 2.0…
Any feedback is welcome before we release it officially to Grails.org.
Indeed, it looks like Grails Facebook-graph plugin does not support OAuth2 Facebook authentication (which is required since October 1st 2011).
We have already ported the official PHP SDK V3.1.1 to ColdFusion 9 (https://github.com/affinitiz/facebook-cf-sdk).
Last month, we started to implement it as a plugin in Grails 2.0.
It is currently at an alpha stage so we have not released it yet, but it is working on our prototype.
To connect to the Facebook Graph API, it uses RestFB internally.
If you want to give it a try and give us some feedbacks, let me know, I'll sent it to you by email.
Anyone who can point me into the right direction? Tried to ask this question over a the Kaltura-forums with no answer. I get this error when I try to register Kaltura CE in Moodle:
"Your Kaltura registration failed.Missing KS. Session not established"
The Kaltura CE installation is working with Drupal, but I cannot make it work with Moodle.
By looking at the code it seems like Moodle is trying to register in order to set up a "Kaltura session" aka KS (via cURL) with the Kaltura CE-server. The installer seems to send the wrong parameters.
KalturaCE v.3
Moodle 1.9.9+
Kaltura Moodle Plugin
Has anyone got the Kaltura-plugin for Moodle to work, if that's the case which versions of KalturaCE and Moodle were you using?
Regards, Jan
There is some kind of resolution for that problem posted here: http://www.kaltura.org/config-moodle-mod-moodleadmin-page