101
geekwright
Re: WTF Shareoholic!

You will need to set up an "Inline App"

Down at the bottom of the Site Tools Dashboard there is a drop down labeled "Add Inline App Location" - select the "Share Buttons" option. You can control what services are included, styles, alignment, etc.

You may have to edit the individual templates to add the new data-app-id to see the results. There is some default behavior going on there, but I don't know the rules for sure.



102
geekwright
Re: WTF Shareoholic!

Shareaholic is the service used by xBootstrap to provide the social links for sharing content. You see those when viewing an item in Publisher, as an example.

Shareaholic has added new options and the default settings are resulting in that pop up ad section.

You can remove the Shareaholic code as sabahan mentions above. That will kill the ads and the social links.

If you want to preserve the social links, you can create an account and register your site on shareaholic.com to take control of the settings.

Once you have registered your site, edit themes/xbootstrap/tpl/shareaholic-script.tpl

Find the line reads:
var apikey = '4b44261173043ae4c20b8aef56d4521d';

Change that 4b44261173043ae4c20b8aef56d4521d to the site id Shareaholic generated for your site.

You can then change the settings for the site in the Site Tools Dashboard (i.e. turn off Anchor Overlay Ads.)

You can also customize the social links by creating an Inline App. To implement these changes, edit the template you want to customize (i.e. in themes/xbootstrap/modules/publisher/publisher_item.tpl). Locate the div with these attributes :
class='shareaholic-canvas' data-app='share_buttons' data-app-id='482507'

Replace that line with the code snippet generated by Shareaholic for your inline app.

The current plan for the next release will change this feature in xBootstrap to require explicit opt-in, requiring the admin to supply the site id.



103
geekwright
Re: Bulk user registration with xoops 2.5.8.1

Try this script: import_users.php

It uses system handlers, so it should work in more modern systems.



104
geekwright
Re: mysql_real_escape_string XOOPS replacement ?

The BEST way is to do this:
$employee_id $xoopsDB->escape($_GET['id']);


That will continue to work no matter what the underlying database driver is in the future.

Quote:

mjoel wrote:
since mysql_real_escape_string is deprecated

if i have this code
$employee_id mysql_real_escape_string($_GET['id']);

what should i replace it with



105
geekwright
Re: mysql query with XOOPS 2.581

There was a stray semicolon in while condition. This should do it.
$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>'
}



106
geekwright
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.



107
geekwright
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 ?



108
geekwright
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.



109
geekwright
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 allhttp://example.com tohttps://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.



110
geekwright
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.




TopTop
« 1 ... 8 9 10 (11) 12 13 14 ... 22 »



Login

Who's Online

200 user(s) are online (156 user(s) are browsing Support Forums)


Members: 0


Guests: 200


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