11
vamptrix
Re: PHP 5.5 is dead: time to move to PHP 5.6 and PHP 7
  • 2016/7/13 6:03

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


I'm doing the best I can to help translating and writing documentation - if you can read and write, you can help XOOPS :)!



12
vamptrix
Re: Biblioteka problems
  • 2016/7/7 13:32

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


Looks like your upload limit of your server isn't set correctly.

What's your PHP max post and max upload size?



13
vamptrix
Re: how to protect single custom page ?
  • 2016/7/4 5:56

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


Quote:

Mamba wrote:
Quote:
I think that's a bit overkill (in terms of resource usage) for 1 page, but yeah, that does work.

One way or the other, you need a module, in order to take advantage of the Permissions (even when using XMF that you've linked to). You can create a new "dummy" module and add the page there, which probably would take you at least 30 minutes, or you can clone an existing module, which would take only 5 minutes, and be done with it.

To be honest, I am less concerned about the resources than about effective use of my own time


And I can understand that :). However, we should really make a module for things like this. Once I'll get the hang of it, I'll try to look into this.



14
vamptrix
Re: how to protect single custom page ?
  • 2016/7/1 13:46

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


Quote:

Mamba wrote:
I would just put this page into a module, where I have a full control of permissions.

For example, I could clone a Publisher, add this page as an article, set the permissions to specific groups, and I'm done.


I think that's a bit overkill (in terms of resource usage) for 1 page, but yeah, that does work.



15
vamptrix
Re: how to protect single custom page ?
  • 2016/7/1 10:03

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


That could be done with XMF, if you're using XOOPS 2.5.8.

Take a look at https://xoops.gitbooks.io/xmf-cookbook ... k/recipes/perm-check.html, this should be able to do what you need it to do.



16
vamptrix
Re: Modern documentation about general usage / People needed
  • 2016/6/30 7:33

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


Mamba, could you add my user "kevinpetit" to the XOOPS organisation?



17
vamptrix
Re: Modern documentation about general usage / People needed
  • 2016/6/27 15:20

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


Quote:

Mamba wrote:
Quote:
The big issue with GitBook is that it's a book: it's hard to search inside of it, and if you need information about something, it's hard to find it (unless you know how or where to find it/in which GitBook it is).

It seems to me that you didn't spend any time of GitBook

Why are you saying that it's really to search inside of it???? What is wrong with the search inside a Gitbook?

And if you want to link several GitBooks into one, you can do it as well. The process is the same everywhere else:

a) you can have several small books, or
b) you can create a one monster book

Quote:
And you can export it to HTML too.

What do you mean by that??? The Gitbook is HTML as default:
https://xoops.gitbooks.io/xoops-installation-guide/content/


It looks like I lept to conclusions too soon - I have used Gitbooks before, but it didn't work as well back then. It look like it has improved quite a lot :)

I take back all my problems with Gitbooks ;).



18
vamptrix
Re: Modern documentation about general usage / People needed
  • 2016/6/27 10:48

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


Quote:

And what's wrong with GitBook?

- One single, easy to read and write, Github rendered source format (i.e. Markdown) for different output formats such as HTML, PDF, MOBI, EPUB,

- A documentation build is triggerable via Github Webhook, i.e. you can edit the documentation either with the GitBook Editor and it will upload the changes to GitHub, or you can make the changes on GitHub, and it will trigger rebuild of the book, so the readers will always have the latest and greatest version of the book, and you can choose whatever method you prefer to make changes.


The big issue with GitBook is that it's a book: it's hard to search inside of it, and if you need information about something, it's hard to find it (unless you know how or where to find it/in which GitBook it is).
GitBook is really good for specific information about 1 thing, like a module. But for general documentation, e.g. setting up your site, getting your rights set up and all basic XOOPS things, I think that a Sphinx documentation site would be better.
Examples of Sphinx documentation are CodeIgniter, ReadTheDocs etc. It's really clean, fast and easy to maintain/edit.
And you can export it to HTML too.
And the search is really good too ;)



19
vamptrix
Re: Losing revenue because of Adblock?
  • 2016/6/27 8:33

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


I don't really think that there is a module that does this and this is something that has only been an issue for the last few years (as adblockers weren't such an issue years ago).

With the overhaul of XOOPS that's currently going on, I don't know if these modules still work - however, this might be something that we could look into later.

Kev



20
vamptrix
Modern documentation about general usage / People needed
  • 2016/6/27 8:30

  • vamptrix

  • Theme Designer

  • Posts: 424

  • Since: 2008/5/3 1


Hello everybody,

Currently, work is underway for XOOPS 2.6, and in order to get documentation ready before it's release we should start working on the documentation now - XOOPS 2.6 changes so many things that I feel it's best to start over with the documentation (with the exception of the existing documentation on GitBooks).

I suggest (but this is entirely open for discussion) that we use Sphinx/ReadTheDocs to create this documentation - this is a modern system that's used by quite a lot of projects, it delivers clean and easy to update documentation and it has search capability. I think this is the perfect solution to get new documentation out. What do you guys think about this?
One handy thing is that we can provide a copy of the documentation with the XOOPS download package itself.

I've been really busy over the course of the last year. Before this period I started working on documentation already, but that was focussed on XOOPS 2.5.x - but since 2.6 is coming closer it might be better to start over again and create entirely new documentation.

I can't do this entirely on my own though - so if you want to help me create this new documentation, please feel free to do so.

Kev




TopTop
« 1 (2) 3 4 5 ... 18 »



Login

Username:
Password:

Lost Password? Register now!

Who's Online

63 user(s) are online (38 user(s) are browsing Support Forums)


Members: 0


Guests: 63


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits