Thanks, Howard, I appreciate your insight.
Re: keep Google search-robots outside
Re: keep Google search-robots outside
2 cents on robots.txt ...
Works only if the bots honors it ... and the bots/restrictions listed in the robots.txt file. There are some 'research bots' ... that's what they claim anyway ... that might access it and then totally ignore it.
Otherwise that file ... accessible by anyone on the planet and a browser ... could see what it is you are trying to protect ... the rules. So, in a way, one is providing a roadmap for all to see.
In the case of Google, it will take some time for all of the google bot network to honor robots.txt ... a week or so to finally see in logs no access by google bots isn't unusual.
Even though, robots.txt might be the 'easiest' way ... but it's not 100%. :|
'spirit of sharing', Ken
Re: keep Google search-robots outside
Thanks Ken.
I will continue using a robots.txt in every Moodle-installation, that I want not to appear in any search-Results of Google. I understood, that a few days are needed for crawlers to accept that.
Thank you Ken and other Helpers again.
I hope I will succeed.
Rolf
Re: keep Google search-robots outside
In Admin, Security, Site security settings, their is an option "Open to Google" whose default is No. There is a second setting "Allow indexing by search engines." I now wonder how thorough these two settings are, if you set them to "No" and "Nowhere," in blocking robots and Google?
Re: Error when Installing Joomdle
Worked like a charm! Thank you!
Question - should I not update Moodle until this bug is solved?
Thanks again!
-Reuel+
Re: keep Google search-robots outside
Please see:
https://support.google.com/webmasters/answer/80553?hl=en
and
https://productforums.google.com/forum/#!msg/webmasters/4fKthSy7oFQ/GgslLXJnDQAJ
and
https://www.lifewire.com/what-is-the-ip-address-of-google-818153
not sure the above links say the same things ... but do know Google is massive and can be aggressive ... or it at least might appear to a webmaster/moodle admin/blog admin, etc. 'targeting' their sites ... but are they?
Am a log watcher myself due to the fact there were no really good tools to automate logwatching back when I started ... yes, am ancient. But, what I've learned from doing things that way has 'educated' ... and I know there are some who will disagree with the next ...
If bots are causing no harm (not stealing your content/web whacking) other than being annoying doesn't the moodle admin/server person have much more important concerns? Keep your servers up to date and your apps up to date and the moodle up to date and your certs up to date .... then sleep at night!
Just my 2 cents!
'spirit of sharing', Ken
Re: Installation Problem with Moodle 3.4.1
I have the same issue here , but I'm using wamp
Re: keep Google search-robots outside
Yep Ken, thanks. I would much rather be watching what my students are doing than what web robots are doing.
But I also enjoy pausing a moment an trying to learn something new.
Re: keep Google search-robots outside
You are all quiet right, but I have a normal Website beside some Moodle.
In Searchresults regarding searching that address/site, I do not want my Moodle-stes to appear.
Rolf
Re: Error when Installing Joomdle
Great news! The bug only occurs during the plugin's installation so once installed you should be able to use the unmodified Moodle source code to keep your site up-to-date.
SMTP + SSL Configuration Problem [certificate verify failed]
Hello,
I am receiving the following error when configuring SMTP with TLS in our Moodle Server:
Using our exchange server as a relay.
Moodle Version: 3.5.2+ (Build: 20180927)
Using a XAMPP build.
---
2019-01-30 15:07:06 Connection: opening to XXXXXXXXXXXXX:587, timeout=300, options=array()
2019-01-30 15:07:06 Connection: opened
2019-01-30 15:07:06 SERVER -> CLIENT: 220 XXXXXXXXXXXX Microsoft ESMTP MAIL Service ready at Wed, 30 Jan 2019 16:07:06 +0100
2019-01-30 15:07:06 CLIENT -> SERVER: EHLO xxxxxxxxxxxxxxxx
2019-01-30 15:07:06 SERVER -> CLIENT: 250-XXXXXXXXX Hello [XXXXXXXXXXX]
250-SIZE 52428800
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-AUTH GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250 CHUNKING
2019-01-30 15:07:06 CLIENT -> SERVER: STARTTLS
2019-01-30 15:07:06 SERVER -> CLIENT: 220 2.0.0 SMTP server ready
2019-01-30 15:07:06 Connection failed. Error #2: stream_socket_enable_crypto(): SSL operation failed with code 1. OpenSSL Error messages:
error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed [C:\xampp\htdocs\moodle\lib\phpmailer\src\SMTP.php line 403]
2019-01-30 15:07:06 SMTP Error: Could not connect to SMTP host.
2019-01-30 15:07:06 CLIENT -> SERVER: QUIT
2019-01-30 15:07:06 SERVER -> CLIENT:
2019-01-30 15:07:06 SMTP ERROR: QUIT command failed:
2019-01-30 15:07:06 Connection: closed
2019-01-30 15:07:06 SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
---
I've found several forum posts and articles online with the same error, but the problem is that I'm a complete PHP beginner. My question is; where can I define where the SSL cert is located?Is it in the php.ini or in the PHPMailer.php? Or should Moodle automatically read it out of the Windows Cert Store on the server?
Any assistance on the matter is very much appreciated.
Thank you in advance!
Transfer to subdomain
I run Moodle 2.6.5 at pediatrichospitalist.org via a hosting commercial host, Site5. Because I transferred the site from another host, the current site was not created with their web app system, which has led to difficulties upgrading to newer Moodle versions.
I am trying to move the current site to a subdomain so as not to lose our work. Under the direction of their tech support, I created "old.pediatrichospitalist.org" and moved the site files in public_html into the subdomain folder.
As a result, the site would not load at the subdomain ("incorrect access" error). Tech support told me I needed to "update links from the backend" myself because they are "not familiar with your website requirements and scripts."
I would greatly appreciate any recommendations on how to move forward. Basically, I want to build a new site from scratch with a recent version of Moodle, and back up the old site somewhere where it can still be accessed.
Thanks!
Grant
URL not found after install
Re: Transfer to subdomain
You must understand that the vast majority of Moodle administrators here work on the Unix/Linux shell. We don't have an idea of your providers "app" system. Since their support team is involved, they can refer to our documentation do the equivalent in their system.
What you have is a https://docs.moodle.org/26/en/Moodle_migration, or rather a special case. Ask the IT people to compare this with what they have been doing. My guess is that they've overlooked "Change your URL" part in the config.php.
Re: URL not found after install
What's the operating system / hosting?
What did you upgrade from? How did you do it?
What's in the web server error log?
Is it true - if you go to that path in your file browser (or whatever you have) is it there?
Incremental update (3.5.3 -> 3.5.4)
Hello everyone,
I would like to ask whether an incremental update (3.5.3 to 3.5.4) requires the same process as upgrading (e.g. 3.4 to 3.5, or 3.5 to 3.6).
I just took over as the admin of my company's customer-facing Moodle, but unfortunately neither I nor any of my colleagues has any experience of installing or upgrading Moodle.
Our current version is 3.5.3. We want to avoid upgrading until the next LTS version comes out, but it seems sensible to take the incremental update to 3.5.4.
There is plenty advice for upgrading from a previous version, but nowhere in the documentation (AFAIK) is any distinction made between such upgrades and the incremental, bug-fix updates within one version.
Is the process exactly the same? Is any part of the process easier or unnecessary (e.g. can I expect the plugins to work without needing their own upgrades?)
Thanks very much for your time in assisting a novice!
Lee
Re: Open Forum Plugin in Moodle 3.6
- <a href=”https://www.findfreejob.com/” rel=”dofollow”>free Job</a>
Re: Incremental update (3.5.3 -> 3.5.4)
Sticking with a long term support version is a good idea.
Bug fixes for general core bugs in 3.5.x will end 13 May 2019 (12 months).
Bug fixes for security issues in 3.5.x will end 10 May 2021 (36 months).
Official docs are here:
https://docs.moodle.org/35/en/Upgrading
Process is the same for an update or an upgrade - update being an incremental upgrade
like 3.5.x to 3.5.highest at the time.
Depending factors consider using Git for updates or upgrades.
https://docs.moodle.org/35/en/Git_for_Administrators
One major factor ... customizations of core code and addons/plugins.
And for future ... check the environment of your current system.
Admin -. Server -> Environment. Update Component.
Then look at environment requirements for 3.6 and beyond.
Mention this now cause later its sorta outta sight, thus outta mind.
Tne Notifications screen where one sees the growing number
of updates isn't linked to the Environment Check.
Even a minor update might be best done in a clone sandbox server first.
And before pulling the trigger on production server, do a full site backup ...
code + DB SQL dump + data directory. You won't ever regret taking the time to do a full site backup!
'spirit of sharing', Ken
Re: keep Google search-robots outside
Yep Ken, thanks. I would much rather be watching what my students are doing than what web robots are doing.
But I also enjoy pausing a moment an trying to learn something new.
Import error for table mdl_backup_controllers
Greetings,
Moodle Version: 2.3
I am doing an upgrade and need to import a backup of a moodle database into mysql. However I keep getting an error message on the mdl_backup_controllers table:
MySQL: Error 1153 - Got a packet bigger than 'max_allowed_packet bytes'.
Is the data in this table important or can it be deleted without affecting the system?
Is there any other way to resolve this issue? I did some reading where the suggestion was to increase max_allowed_packets in the my.ini file in MySQL. I was hoping to avoid that as many other applications are using this database.