Hey Geekwright, since I last tried the XOOPS 2.6 install on my ubuntu desktop box which is what the code install examples and video should be in, IT WORKED!! so I will play with it later today when the sun goes down, this is only sun up threading... so what I think needs to be changed is the prefix_modules folder to the following as you still haven't yet addressed the planning documents in the [size=x-large]XOOPS Forum - XOOPS Documenting Team[/size] which was released before you where even in the show Richard!!

Currently this is the prefix_modules table



I think we need to update it too the followng at least:

A great application for your own NTP Service bell, remember if you set up NTP, you can use it for your time source for your own PC + Router at home, by enabling on the firewall port 123...

Another Great Application is - ClockSync - for Android Mobile Phone see it here:-

helps to also run:



it will load it and make sure it running when it reboots

hey Xoopstroupers, how are you all, if you didn't know in unix/linux you can specify the /etc/ntp.conf that effects the time retrieval of the server even without ntpd installed; if you want to install NTP Services and Server for example on ubuntu you run the following:

$ sudo apt-get install ntp -y
$ sudo ufw allow 123
$ sudo service ntp start

if you check http://ntp.snails.email you will then be able to add your service into the pooling with the form on there, the hostname needs to be pingable this is only if you install: ntp services

There is a script you can add to a cron to retrieve the detailed /etc/ntp.conf it is:-


You can also change your /etc/ntp.conf to list just as this with the Chronolabs Cooperative as the only pooling:-

pool 0.ntp.snails.email iburst
pool 1.ntp.snails.email iburst
pool 2.ntp.snails.email iburst
pool 3.ntp.snails.email iburst
pool 4.ntp.snails.email iburst
pool 5.ntp.snails.email iburst
pool 6.ntp.snails.email iburst
pool 7.ntp.snails.email iburst
pool 8.ntp.snails.email iburst
pool 9.ntp.snails.email iburst
pool 10.ntp.snails.email iburst
pool 11.ntp.snails.email iburst
pool 12.ntp.snails.email iburst
pool 13.ntp.snails.email iburst
pool 14.ntp.snails.email iburst
pool 15.ntp.snails.email iburst
pool 16.ntp.snails.email iburst
pool 17.ntp.snails.email iburst
pool 18.ntp.snails.email iburst
pool 19.ntp.snails.email iburst
pool 20.ntp.snails.email iburst
pool 21.ntp.snails.email iburst
pool 22.ntp.snails.email iburst
pool 23.ntp.snails.email iburst
pool 24.ntp.snails.email iburst
pool 25.ntp.snails.email iburst
pool 26.ntp.snails.email iburst
pool 27.ntp.snails.email iburst
pool 28.ntp.snails.email iburst
pool 29.ntp.snails.email iburst
pool 30.ntp.snails.email iburst
pool 31.ntp.snails.email iburst
server ntp.snails.email

You can also on your windows or macintosh in the control panel settings under time change the url to: ntp.snails.email!

The reason XOO + OOP is so popular with a /class /include structure in not only PHP, but c++, C Ansi, Perl, Java etc, is the code is transpositional and will become when routed external like on sourceforge.net into someone else gravity well meter maid; the language constructs for their systems, not many MVC do this they are earth specific!

You can always if you like join the Chronolabs Cooperative group, I am and would love too have more than a 2 handed horse in the code repositories for it!! Connect to my Skype so we can chat!

btw. Michael Beck All Abored the Choo Choo Express too newly founded land:~

Look I don't want to shunt the gun at the moment looking at the xoops engine 3.0, but if you ask me and I have a qualified master of science with RMIT with 2008 in IT, Physics + Psychology; ever started pushing for an MVC version of XOOPS which believe me isn't what you find still classically c++, c ansi, perl, java and other languages still follow it the XOO + OOP Structure of being a classes/including folder panagram...

XOOPS 2.6 is good but it still missing and should be written in now the structure is set the requirements in the XOOPS Documentation area for addition requirements for the library to support as well as the upgrade I wrote to convert the database entirely to INNODB to support database 'constraints' in mysql which is in the 2.5/2.6 forums recently by me topically, which increase speed exponentially of the database due to probability predictions in the structure it stores it in from them... Mamba has a copy in his gmail of mysql.sql with all the database root constraints set that need to be added to the upgrade when set in his gmail.com under my name if he searches - Simon Roberts!

It also needs it additional classes for reverse compatibility with XOOPS 2.5 and so on it essential it is an easily walk through and over without the composer call these files should be included only updatable with composer in the distribution master.zip.. Remember Richard, I have always remained off the XOOPS Council; even though I carry ID That would even allow me to list with the American XOOPS LLC as kinda like a moderator mediator cause of the co-relationship between the XOOPS Foundation + Chronolabs Cooperative generally using it for intranet and so on!


I will remain an anonymous veto on what mamba keeps saying it has to be reverse compatible still and all the requirements like XOOPS Documentation met to complete XOOPS 2.6

Honestly if you branded a top end code library not backend library with XOOPS with an MVC route and so on not manually written by the system module as an extra plugin to the root .htaccess, then you would be consider as an XOO + OOP as an MVC as some sort of mental health escapee or day release about on the web!

Quote:



Quote:

After doing the composer which I think should be done for the client as part of the installation also the README.md needs to be written for Ubuntu/Debian..

Anyway as part of the installation I get to: install/page_dbconnection.php ~ and get the following error:

Quote:

I am working on the PHP.ini settings module for system as well as the .htaccess route and API, btw. mamba I looked at those api guides you sent through, and graph is just based on facebook.com graph api and the other one is oauth, there will be later oauth methods, in the api, but I remember when I implemented them in the previous historical corridor, it destroyed oauth2 on twitter and a couple of places and completely collapsed, they are essentially still both REST API just with a control class anyway...