Stuck on Plugins Check - moodle

I tried to install without realising an older plugin than what was already installed. It errored with the install however now I cant get past the check plugins screen to fix my issue.
Reload just reloads the page, update does nothing. If I click Upgrade I get this:
I cant do anything else. If I try to reload Moodle with just http://moodle (Internal URL) I get redirected straight back to this page. If I clear my cookies I get taken to the login page, but after logging in it is straight back to the "Plugins Check" page again.

Do you have administrative access to the server running Moodle?
You should be able to download the version of the plugin you need and unzip it directly into Moodle's directory structure, and then log back in to the Web UI.
In my moodle installation, this is here:
/var/www/html/moodle/course/format/singleactivity
You should be able to get the correct files from the installation package you used. Just make a backup of the existing folder in your Moodle environment, move it to a safe location, and drop the complete folder for the new version in its place. Then reload the web client.

Related

How to to clear the tiki-system cache?

I am using Tiki Wiki, and I change to login with an LDAP server, I already made all the configurations but when I try to login with a user from my LDAP server give me a blank page. I saw a solution on TIKIWIKI doc's, they say to clear the cache but I dont know how to clear.
You can clear the Tiki caches by going to tiki-admin_system.php when logged in as an admin, there is a link on the Settings part of the main Tiki menu, and one on the Quick Admin module (if enabled).
You can also clear the cache from the command line by doing
php console.php cache:clear
More info here
(however, if you are running Tiki 16.2 there is a bug in LDAP which also produces this sort of blank page error. This will be fixed in 16.3 which will be released soon, in the mean time you can download a nightly build from here)

Mbstring extension installation on godaddy server

Call to undefined function mb_convert_encoding(). How to install
mbstring extension installation on godaddy server?
I have found the solution. We need to complete the following steps:
1.Login to your server WHM as root
2.Search EasyApache or go to Software menu after that EasyApache
3. you can see there are some profile. click on customize profile default profile.
4. click on continue to second step
5. On “Step 2,” click on “Exhaustive Options”
6. Under PHP, check the checkbox for MBString
7. Proceed with Build & Compile Process
Make sure you wait for the build to complete.
I'm updating this thread as I went through a painful day trying to get this resolved. The mbstring extension is used by Magento (I needed it for 1.9) and without it installed, the checkout process will fail, with the shopping cart failing to take the user to the 'Thanks for your order screen' (although the order is sometimes created on the back-end successfully). It was also creating an issue when hitting the 'Send Email' button on the Admin panel on an Order, producing a 500 error.
In my log files, I was seeing the following error:
PHP Fatal error: Call to undefined function mb_convert_encoding() in
/home/yoursite/public_html/lib/Pelago/Emogrifier.php on line 556
Searching for this error gave results that suggested I needed to enable the mbstring extension on the server, but with a GoDaddy hosted virtual server, I ran into a wall of frustration with the package not being found via the php install search, and their tech support unable to assist. The above solution worked, although I will clarify the instructions below for the current WHM panel (Jan 2019):
Login to your server WHM as root.
Search EasyApache or go to the Software menu on the left and select 'EasyApache 4'.
You will see a list of profiles and at the top of the list, 'Currently Installed Packages'. Select the 'Customize' button.
Select the 'PHP Extensions' link or keep hitting 'Next' until you reach the page.
In the search box, type 'string', you will see 'php56-php-mbstring' and 'php70-php-mbstring'; move the grey slider on the right to install each.
Continue to the 'Review' tab. Here you can simply hit 'Provision' to install the extension. You can also save these options as a custom profile if you'd like.
After the build has completed, the extension should be available on all your domains.
Hopefully this will save someone some time trying to figure this out!

How to diagnose metro app deployment errors?

When trying to debug a Metro project from VS, I came across this error:
DEP0700 : Registration of the app failed. Another user has already installed a packaged version of this app. An unpackaged version cannot replace this. The conflicting package is PACKAGENAME and it was published by CN=some Guid. (0x80073cf9)
But I have already uninstalled the app from the Start page, also, I can confirm that there is no entry left in Add/Remove program.
And since the access to the "%PROGRAMFILES%\WindowsApps" folder where the app files reside in is blocked, so I have no way to see if the app is still there.
However, I can still find many 'PACKAGENAME' occurances in the registry.
How to diagnose this? How to get rid of the "packaged version" so I can start debugging from VS?
Try installing the app from the windows store again, and then uninstall it from the start page. It appears that when Visual Studio does the uninstall it doesn't do it right.
1) Go to your Package.appxmanifest file in your solution
2) Go to the identity tag.
<Identity Name="xxxxxxx-yyyy-zzzz-tttt-bbbbbbbbbbbbb"
Publisher="CN=bigbob"
Version="1.0.0.0" />
3) Change the value of the Identity Name (Ex from ...bbbbb to ...bbbbc)
4) Rebuild and run
Source:
http://www.sempf.net/post/MetroUIAnother-user-has-already-installed-an-unpackaged-version-of-this-application.aspx
Are you sure you didn't just unpin the app? Try doing a search for it and see if it is still there.
I find a solution to the problem. It's said it is a "staged package" that does not show up in my start page so I can not uninstall it in normal way. I follow the steps, and successfully get rid of that "un-uninstallable" :) package.
This blog post was helpful, although after an hour or so of troubleshooting it turns out that I had indeed installed the package under another user account. After switching accounts and uninstalling from the start screen it worked fine.

Click Once Deployment Error

I am new to Click Once Application deployment so I think I may have a simple problem. I have a window app that I created and deployed successfully as a ClickOnce App using Vis. Studio 2010 and deploying to a web service. I made some changes to the app and changed the deployment location so I started the click Once Process over. Now when I deploy I get an error. The app builds fine, runs fine in VS 2010, when I deploy files are created. Double clicking the App.application file will start the install of the app with a .Net framework error.
"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
System.UriFormatException: Invalid URI: The URI is empty..."
I have double checked and triple checked the Publish Foldre Location and INstallation Folder URL to make sure they are pointing in the correct places and using the correct format. I double and triple checked the Updates dialog box when you click the Updates button. The combobox for the Application Updates matches the Installation Folder URL. "\MyServer\Users\Administrator\Desktop\Transfer\Deploy\" I double checked to make sure the required files are correct. Security settings did not change.
What could I be missing?
It seems you missed one backslash in your installation folder URL:
\\MyServer\Users\Administrator\Desktop\Transfer\Deploy\
Please make sure that if you are using some image/sound or log files then its Build Action must be "Content" type.

SpringSource ToolSuite and Subclipse Plugin

since I use SpringSource ToolSuite 2.7.1 and installed the latest Subclipse Plugin (1.6.x), this plugin ask's me every time I commit something into the repo for my password, regardless I've enabled the 'Save Password' checkbox. As I know, the Subclipse plugin doesn't store the credentials itself, instead use the authentication informations from the underlying SVN adapter so I try the following without any success:
1) delete ~/.subversion/auth
2) delete ~/.eclipse_keyring
After restarting STS the password dialog prompts again every time.
With Eclipse Indigo and the same Subclipse Plugin installed, this strange behavior doesn't happend, the passowrd is taken automatically as expected.
If I use svn from the command line, after I initially enter my passwords, it's used automatically and doesn't annoying me any longer.
Any sugggestions, why this doesn't work under SpringSource Toolsuite ?
Kind regards
Dominik
SOLVED: the reason was, that the STS.app do not has access to the MacOS X KeyChain for the SVN password. So therefor it has to ask again and again. The used Eclipse.app was added as trusted app for accessing the stored svn password. Strangely, I can't add STS.app to the list of trusted apps for the SVS password entry, but thats another question here. If I activate the 'access for every program' checkbox, STS.app is enable to read this password and don't ask any longer !
I don't have much experience with the subclipse plugin. I tried it a few times some years ago and it didn't go well for me. I then switched to subversive. I have not experienced this problem with the subversive plugin, and so perhaps you could try switching and seeing if this will help you.
I would try deleting or renaming the ~/.subversion folder. There are also settings in the config and servers file that can prevent password storage. You also do not mention what access method you are using ... for example passwords are not stored for svn+ssh://
It would also be relevant to know if you are using JavaHL or SVNKit. JavaHL is native Subversion so passwords are cached in ~/.subversion/auth. SVNKit caches passwords in the Eclipse keyring, but I believe it will read from the SVN password cache if it is already there -- or at least used to.
Finally, since it works with Eclipse but not STS (and there should be no reason why) maybe check permissions? Is STS running as a different user for some reason?
The settings for the secure storage are equal. But it seems, that these setting aren't used, the mentioned file doesn't exist. In the meantime I've installed the STS 2.7.2 update and a fresh Subclipse Plugin, but without success, the dialog popups again for every commit. After that, I create a new user, copy the whole STS 2.7.2 install dir including Maven, tc and the just installed Subclipsed plugin to a dir shared for all users. I have to fix the file permissions of the maven subdir due to lack of read permissions for the new user. I checked out a project from svn and modified it. After the initially question for username/password, this dialog don't popups any longer. It seems, that for this new user, things went fine. I switch back to the original user and start STS 2.7.2. from exactly the same place, the shared dir. But ... you predict it ... the dialog popups again and again and again .... It seems to be something wrong with any of my user settings, but which one ? I've delete ~/.subversion/auth and the whole ~/.subversion too. No way to avoid the constant question for the password for the given user. Mhm, strange, any further tips or suggestions ?