xoops forums

Forum Index


Board index » All Posts (geekwright)




geekwright

Quite a regular
Posted on: Today 19:47
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#1

Re: Just not good enough?

We spend a great deal of effort in our coding and testing to make sure that there is a path forward from version to version. There will be hicups from time to time, but in the end, things work.

As an example, this site is running our current development branch of XOOPS 2.5.9, currently still in a beta stage. It is near release, but not quite. This site has data preserved over many years, moving forward with each new version. We have a great deal of confidence in our product.

Here are a few things to keep in mind as you plan your upgrade.

Make backups of your full site and your database before starting. You can always restore service by restoring you backups if things don't work as expected.

Check for more current versions of the modules you use. Newer versions of modules may fix issues that occur because of changing technologies, or be tailored specifically to support newer versions of XOOPS. Start with upgrading XOOPS, and then update the modules individually. Most modules have the same attention paid to upgrades as XOOPS does.

As a community, we have a lot of experience in upgrading, and most of us are happy to share our expertise and help out.

Looking at your site (BTW, that is an awesome topic focus!) it looks like it should go smoothly. XOOPS 2.5.1 is old, but no where near the oldest we've seen. And the modules you use are still maintained and have recent updates.

If you decide to go ahead with an upgrade, your site could be responsive and mobile ready fairly quickly.


PS - regarding the long lines on preview, there seems to be a simple template issue in newbb, nothing to serious and it should be resolved soon.


Quote:

LonesomeTwin wrote:
Hello everybody.

I'm looking to upgrade my old forum site so that it has more web content and more importantly works well on a smartphone. It's currently V2.5.1a, is it safe/possible to upgrade it to a newer version and then install a responsive theme over it without losing all the posts? While I'm at it would also like an auto-resizer so that people don't keep downloading 2M pics because they can't resize them themselves. One option I've been exploring is redoing the whole thing in Wordpress and then trying to port the database over, but WP forums are pretty rubbish.

Many thanks for any input - Steve

The Lonesome Twin

ps. On previewing this post the text box spread over the edge of the screen, doesn't inspire confidence.


geekwright

Quite a regular
Posted on: Today 18:39
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#2

Re: mysql query with XOOPS 2.581

As of version 2.5.8, XOOPS no longer uses the deprecated mysql extension, so the mysql connection that is required for calls like mysql_query() does not exist. This change was required to make XOOPS work with PHP 7.0 and above, where the mysql extension was removed. (See this page on supported versions of PHP to understand why that is important. Time is running out for PHP 5.)

The best approach in this case is to rewrite the code to use the standard database connection calls. It would look something like this (not tested, just off the cuff.)

$result $xoopsDB->query('SELECT * FROM ' $xoopsDB->prefix('myunit'));
if (
$result===false) {
    die(
$xoopsDB->error());
}
while (
$row $xoopsDB->fetchArray($result);) {
    echo 
'<option value="' $row['list_unit'] . '">' $row['list_unit'] . '</option>';
}


Quote:

mjoel wrote:
I have this query code in one of my custom page in XOOPS 2.572..and its working fine but when i upgraded to XOOPS 2.581 recently this no longer work..the page is not fully load and it stopped at this query

$resultmysql_query("SELECT * FROM ".$xoopsDB->prefix("myunit")." ") or die(mysql_error());  
        while (
$row mysql_fetch_assoc($result)) { 
            echo 
'<option value="' $row['list_unit'] . '">' $row['list_unit'] . '</option>';
        } 
        
?>


what might be the problem ?


geekwright

Quite a regular
Posted on: Today 16:56
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#3

Re: Publisher Clone & xBootstrap Module

Quote:

Zap_English wrote:
I tried that once and it didn't work


Works perfectly here. Not sure what might have gone wrong for you.

Started with clean publisher. Copied everything from hthemes/xbootstrap/modules/publisher to modules/publisher/templates. Install publisher and clone it. Don't forget to clear smarty caches if you have been playing a lot.

That process you described is exactly what the clone process does. It isn't magic. It depends on consistent naming, and just copies files with changed names and replaces specific text in the files to create the clone.


geekwright

Quite a regular
Posted on: Today 15:52
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#4

Re: http to https

Quote:

aerograf wrote:
The ssl problem with mixed content, and decide now with the editors that have inserted links users excluding http: //. But not everyone supports ssl therefore looking for a solution through the above or /redirect.php?site=.
But not everything is working correctly.
Do ideas and solutions?


For internal links, where http links to your own site's content are embedded in your content, you can dump the database, replace all the occurrences, (i.e. change all http://example.com to https://example.com) and then reload it. There are also tools to do that in-place in the database. It is a one shot task, and really should only take a few minutes.

For external links where you are essentially hot linking someone else's content, you either accept the warnings, or you implement some sort of proxy. That is expensive (you end up carrying bandwidth to fetch and send out resources from the other sites, up from 0% to 200% of the cost) and it is risky, you have to engineer in protection to keep your site from being used as a proxy by other sites (a situation that could consume an entire month's bandwidth for a low price hosting plan in a matter of minutes.)

If you had a robust cache strategy, you could cut down the resource requirements. We do something like that for oEmbed content in XOOPS 2.6 already. That concept could be adapted to handle http proxying for this situation. But, 2.6 has a much more scalable cache already. It also has a more modular text sanitizer which could help in implementing the details.

It isn't impossible, but it is not something everyone would want to put into place. At this point, it isn't feasible to dedicate that much additional effort to the 2.5 series.

If the basic support for self hosted content over SSL doesn't work, that is a bug and will be fixed. A comprehensive proxy solution for remote hosted content is an enhancement which will be deferred to the next generation of XOOPS.


geekwright

Quite a regular
Posted on: Today 12:35
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#5

Re: Error during a sending of e-mail with a module or others

I looked into this issue.

Testing used a stock XOOPS 2.5.7.3 and xForms 1.21. XOOPS was configured to use PHP mail(). The only way I could get the error about "could not instantiate mail function" was when the sendmail program (or another suitable mail transport agent) was not installed, or the the PHP ini setting for sendmail_path was incorrect.

See: http://php.net/manual/en/mail.requirements.php

I do not understand how this would have changed with the upgrade, so I am not sure what to suggest.


geekwright

Quite a regular
Posted on: 2/18 16:40
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#6

Re: http to https

Quote:

goffy wrote:
...
Ok, then I will test it and report if I have problems.


Please do! It is important that XOOPS fully supports SSL.

The only issue I am aware of is inconsistent handling of the secure flag on cookies. Patches are in for session and remember me cookies. There are others, but they present less of an issue and are not being changed at this time.

If you do find anything else, please let us know. We really need it to work correctly.

Thanks!


geekwright

Quite a regular
Posted on: 2/18 16:17
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#7

Re: http to https

Quote:

aerograf wrote:
...
And if you use rekaptcha In the File /class/captcha/recaptcha/recaptchalib.php correct line:
function recaptcha_get_html ($ pubkey, $ error null, $ use_ssl true)

...


Thanks for reporting this! This appears to be a safe change even if you are not using https for your main site, since it affects the URL for Google API. I've added this change to version 2.5.9. The replacement, Recaptcha v2 is supported there already, and always uses https.


geekwright

Quite a regular
Posted on: 2/3 23:28
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#8

Re: Publisher Default Image

Quote:

Zap_English wrote:
...
And I'm using clones of Publisher, which xBootstrap doesn't handle.
...


xBootstrap's look comes from override templates in the theme. The theme's templates need to be cloned, too. The publisher clone process does NOT do that.

When you clone publisher, it creates clones of all of its templates under the new name. You would have to manually make a copy of the xbootstrap/modules/publisher folder and templates to match the new cloned name.

For example, if you clone "publisher" to "pubclone" then you need to copy xbootstrap/modules/publisher to xbootstrap/modules/pubclone and then rename all the templates from publisher_*.tpl to pubclone_*.tpl. Also, there are things in most of the templates which will need to be adjusted, too - variables like $publisher_url, included templates like db:publisher_header.tpl, css class names publisher-*, and constants _MB_PUBLISHER_* would all need to be changed too.

The clone function makes a lot of little changes to the files. It would probably be possible to make a "clone publisher templates in a theme" function based on the existing cloning code, but it could get messy.

Crazy idea that should work. You could copy the xbootstrap/modules/publisher templates directly into the publisher/templates directory and then clone it. That way the cloning process would make all the needed changes. The only downside would be that any clones would be locked into xbootstrap -- not really a problem if that is what you are using. Might be worth trying.


geekwright

Quite a regular
Posted on: 2/1 21:29
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#9

Re: The old themes in XOOPS core

Quote:

LioMJ wrote:
what is the plan for these theme ?

We have been plotting this out for some time. (That's why I have not done much with theme selector PR. Most of what it touches will not be in the next release.)

On the front facing themes, sucio and zetagenesis will be gone. The default theme will remain, as we do need to maintain legacy theme compatibility in 2.5.9, and the default theme will serve as a reference for testing legacy compatibility.

The plan is to add two new bootstrap based themes. There is still one slot open, so if you know of a general purpose bootstrap theme that will serve as an inspiration for the new XOOPS user, and will be easy to customize, please suggest it!

On the admin side, the changes have already been made based on known usage.


geekwright

Quite a regular
Posted on: 1/25 9:09
geekwright
geekwright (Show more)
Quite a regular
Posts: 202
Since: 2010/10/15
#10

Re: Remember Me and Public Suffixes

Quote:

Zap_English wrote:
...
I have 4 sites and only this one doesn't work

rfu.in.ua


OK, I see the issue. Here is the cookie arriving at the browser:
Set-Cookiexoops_userxxx=xxxexpires=Thu25-Jan-2018 13:14:58 GMTpath=/; domain=.in.ua


.in.ua is a public suffix. It has the same meaning for setting cookies as a top level domain, i.e. .com, the same as .co.uk

For security, browsers will not accept cookies for domains that consist of only a public suffix. The cookie is being sent, but is rightfully ignored by the browser.

XOOPS 2.5 does not properly handle public suffixes. The code which attempts to determine the domain to use for cookies is obsolete, and produces incorrect results in cases like this.

For this case, I would recommend hacking the "XOOPS_COOKIE_DOMAIN" define,

In include/common.php, line 98 looks like this:
define('XOOPS_COOKIE_DOMAIN', (strpos($domain xoops_getBaseDomain(XOOPS_URL),'.')) === FALSE '' '.' $domain); //by arion92fr

Change that to read:
define('XOOPS_COOKIE_DOMAIN''rfu.in.ua');


With that change, the remember me functionality should work.

This issue has been addressed in part in 2.6 with public suffix list awareness. Also, the XOOPS_COOKIE_DOMAIN should be configured at installation, rather than on the fly. I'll look and see what can be done to help in the 2.5 series.

Sorry I didn't pick up on that sooner. Hope this helps.



TopTop
(1) 2 3 4 ... 12 »