justinebaby wrote:
thanks,
But my probleme, i think it become:
style="background-image: url(<$post.image>);"
and the image from this can't be readed.
As in my previous post, the modules useds: RMcommon and Mywords.
Regards.
justinebaby wrote:
Hello,
I try with your instruction, but some of images do not display correctly. Do you have somme idea else?
Regards.
geekwright wrote:
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.
#Links rewrite
RewriteRule ^ rew /(.*)$ http: // $ 1 [L]
RewriteRule ^ rews /(.*)$ https: // $ 1 [L]
href = "/ rew / www.site ....
RewriteCond% {HTTP_HOST} ^ yurl.org
RewriteRule (. *) Https://www.yurl.org/$1 [R = 301, L]
RewriteCond% {THE_REQUEST} ^ [A-Z] {3,9} / index .php HTTP /
RewriteRule ^ index .php $ https://www.yurl.org/ [R = 301, L]
function recaptcha_get_html ($ pubkey, $ error = null, $ use_ssl = true)
Mage wrote:
Hi Heyula!
Thanks for your great work in templates!
1. I will integrate this
2. With the new system "fineupload" of 2.5.9 I will be able to make the modification to integrate images.
3. I do not know if it's very useful for everyone...
The next version of TDMDowloads will only be a code change to be compatible with version 2.5.9.
Then I integrate the requests!
For the moment I concentrate on xoops 2.5.9.
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|
