21
Peekay
Re: Random Quotes
  • 2013/6/27 9:11

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


As much as I understand the desire to have modules that work with the latest core changes, people will not develop new modules for Xoops unless they are encouraged to do so. If Chefry did draw Mamba's attention to his module, it is not exactly encouraging to have it re-written and then re-published without being given the opportunity to upgrade it himself.

Of course it is quicker and easier for a maths teacher to do a student's homework than to teach maths, but Xoops is supposed to be a development platform as well as a solution. I remain concerned that is is losing its way in respect to this.

As to the spirit of sharing, I think the point has been missed. Legally, the GPL allows me to take the entire module pack that Mamba has worked on and re-publish every module under my name without touching a single line of code. The spirit of sharing however - in fact the spirit of open source software development - is that the experienced share their knowledge to help the less-experienced and provide the original code to help them learn.



22
Peekay
Re: QR Code Generator
  • 2013/6/9 11:55

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


The block only picks up the Publisher info when it is displayed on the Publisher module page alongside the article. Displaying the block on the homepage for example, you will probably just get the link.

Note that due to the way some QR Code readers work, the link may not be clickable when testing the site on localhost. Should work properly on your live www server.

I can't recall if there's a setting to change the QR dimensions. If not, you will just need to make the column a little wider in the theme or CSS.



23
Peekay
Re: The need to keep XOOPS module development in one location
  • 2013/5/15 11:18

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


I notice dev.xoops.org has now gone (blank page)?



24
Peekay
Re: The need to keep XOOPS module development in one location
  • 2013/5/14 13:47

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Quote:

jlm69 wrote:

...To be honest with you I hate sourceforge and svn, you can't beat clicking on a link and getting the download, no need to have special software...


I agree that dev.xoops.org was easier. Anyone who could click a link and make a forum post could be involved in the bug-fixing process.

I imagine SVN is great when programmers collaborate on a project like Xoops core, but it is ordinary Xoops users who often spot errors. I would imagine SVN dissuades many people from obtaining the module BETAs in the first place.



25
Peekay
Re: Permissions problems with 2.5.6 RC 1
  • 2013/4/17 22:33

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Quote:

Mamba wrote:
We've made some security related changes in XOOPS 2.5.6, which will require slight changes to few existing modules in the permission area.

Mamba, I confess I am a little disturbed by this comment. The user and group permissions features of Xoops is probably the one and only thing that sets it apart from other CMS solutions. It has worked flawlessly for years without any security issues that I am aware of. Tinkering with this and causing a failure (which has clearly happened) is not good to see. Why exactly have these changes been made and to what benefit?.

Quote:
This will be documented in the release information on how to make those changes yourself, but all the modules that are part of the Basic Module Pack, will be certified for XOOPS 2.5.6

That is very nice, but surely the path change alone will cause many other modules to fail?. This dependence on 'official' module packs is damaging Xoops reputation as a development platform. This type of change should have been documented *before* this particular version of Xoops was released.



26
Peekay
Re: Using Tiny as custom block editor - preview shows old content.
  • 2013/3/27 12:21

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Tiny bump. Can anyone confirm this?



27
Peekay
Re: xPayment 1.52 bug report
  • 2013/3/23 16:21

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


I cannot test these modules at present, but surely the payment gateway module is intended for the site operator to offer premium (paid for) ads?.

Allowing classified advertisers to set their own Paypal payment link would indeed be dangerous for the site operator. Paypal's IPN system is not infallible and sadly there are a lot of bogus advertisers out there.

Other than providing a contact form, I would let the advertiser and the buyer do their own payment deal well away from your site and state that your site is just for placing ads. It might seem like a nice idea, but if your website facilitates the payment system for goods or services that don't materialise, you could be heading for a lot of trouble.



28
Peekay
Re: Private Messaging - another pref request
  • 2013/3/19 9:04

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Quote:

Peekay wrote:

As a matter of urgency (IMHO) a patch is needed for 2.5.5 so that the 'code' and 'quote' tags will display back-slashes....


That's the problem. I added a back-slash and Xoops CODE tag deleted it.

Quote:
The back-slash needed in the above fix is not visible, so the best I can do is tell you it is needed between the ';' and the double-quote at the end of the anchor tag.



29
Peekay
Using Tiny as custom block editor - preview shows old content.
  • 2013/3/18 12:20

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


The 'preview' button now pops up a JS box which is very pretty, but unfortunately it contains the existing published block text, not the text being edited.



30
Peekay
Re: Private Messaging - another pref request
  • 2013/3/18 11:13

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


That works Irmtfan, but only if you leave the escaped double-quote in the anchor tag, otherwise it's a blank page.

Change:

$block['sslloginlink'] = "<a href="javascript:openWithSelfMain('".$xoopsConfig['sslloginlink']."''ssllogin'300200);">"._MB_SYSTEM_SECURE."</a>";


To:

$block['sslloginlink'] = "<a href="javascript:openWithSelfMain('".$xoopsConfig['sslloginlink']."''ssllogin'300200);">"._MB_SYSTEM_SECURE."</a>";


I have been removing that link manually for years. Many thx for this fix. Just need the same now for user.php. Gonna take a look at it this weekend.

** EDIT **

As a matter of urgency (IMHO) a patch is needed for 2.5.5 so that the 'code' and 'quote' tags will display back-slashes. I have drawn attention to this bug before. The back-slash needed in the above fix is not visible, so the best I can do is tell you it is needed between the ';' and the double-quote at the end of the anchor tag.




TopTop
« 1 2 (3) 4 5 6 ... 187 »



Login

Username:
Password:

Lost Password? Register now!

Who's Online

72 user(s) are online (49 user(s) are browsing Support Forums)


Members: 1


Guests: 71


heyula,

more...

Donat-O-Meter

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

Latest GitHub Commits