The forum is here for legacy reasons. No new posts will be created. User registration is disabled! If you have any questions, please email us or check https://www.adultscriptpro.com for more details!
You are not logged in.
Just done more test again. My feeling is that it is the 12-hour system which makes the problem.
Here is what I found.
Videos added between 00:00 - 00:59 will change to 12:00 - 12:59
Videos added between 13:00 - 13:59 will change to 01:00 - 01:59
Videos added between 14:00 - 14:59 will change to 02:00 - 02:59
....
and finally,
Videos added between 12:00 - 12:59 will remain unchanged
If I look at the column add_date, it is a 12-hour system without mentioning it is am or pm.
So, my guess is that using 24-hour system may fix it.
Sorry, I think I have described the bug a bit wrongly
The timestamp might not be set to the server time. I have not checked it. It seems that it set to the same time from pm to am.
For instance, if the video was added at 20:00, add_time will be set to 08:00 automatically after I edit the video. This may explains why, for videos added in the morning (with respect to the timezone set in ASPRO script), the add_time is not changed after editing them.
Yes, symtab you are right.
I have tried to checked the add_time before and after I edited a video. The add_time changed after I edited the video.
I have posted this before but after some more test, I can reproduce the bug on my server.
After a video is upload, there will be no problem.
However, when I try to edit it in the admin (change the name of it / choose another thumbnail as the first one to show in front end, say), the timestamp of add_time will be automatically set back to the server time zone. Yet, the add_date was kept unchanged. I have set the time zone in admin section, and the time zone set is different from that of the server time.
I have exactly the same problem. And I have try all the possible setting of FTP ROOT yet there is still no luck.
the absolute path of the tmb directory in my case is
/home/username/public_html/media/videos/tmb
and the home directory of the ftp user is
/home/username
And if I am correct it should be
public_html/media/videos/tmb
for the FTP ROOT.
but it does not work at all.
And I have also check my php modules using php -m in ssd. the module ftp is there.
So is there anything I need check?
Just curious, is it better to use apache or nginx or lighttpd if the server is for video streaming only?
Thanks symtab.
Should I choose Pseudostreaming in Vidoe:Sever:Add:Streaming Method?
How about the Lighttpd URLand Lighttpd Secure Download as I am not using lighttpd?
I am not sure about the video server setting.
If I want to use Nginx for streaming, do we just install nginx with the streaming module and nothing else on the video server?
And which Streaming Method should I choose? It seems that I should choose Pseudostreaming but it ask for some lighttpd details....
And also, what should I put for the URL field?
Thanks!!
Thanks symtab. Incapsula only requires me to change the CNAME of my www.my-domain.com to cdn.domain.com and change the A record of the naked domain "my-domain.com". So, is it that I should make the CDN_URL cdn.domain.com in cdn.php?
I am totally new to CDN. I have just signed up a free account on Incapsula and hoped to test with it.
It seems that I need to change the cdn.php file
However, instructions from Incapsula only require me to change the DNS record of my domain. And there is no option for me to upload files to their server. (I read in cdn.php that I need to upload the files in /templates/ in order to make it to work).
So, I would like to know what I need to set in order to use the CDN....
Apparently I have found a solution. limit_conn won't work if we use something like
location /media/videos/mp4 {
limit_conn perip 10;}It is because Nginx will keep on searching the query and the *.mp4 files will be eventually handled by
location ~ \.mp4$ {....}And it won't work even if we put location /media/videos/mp4 {} below location ~ \.mp4$ {....}. It is because Nginx will already handle the *.mp4 files when it finds location ~ \.mp4$ {....}.
So, there is no point to put location /media/videos/mp4 {} in the conf file unless you want to limit the connections to files other than *.mp4 in this directory.
The situation is similar for media/videos/flv and media/videos/mobile
On the other hand, we cannot use
location ^~ /media/videos/mp4 {
limit_conn perip 10;}because Nginx will stop searching the query in this case.
In this case,
location ~ \.mp4$ {....}will not be used to handle the *mp4 files and thus the secure link will not work.
So, we need to do is to add limit_conn at the end of "location ~ \.mp4$", like this.
location ~ \.mp4$ {
..........
limit_conn perip 10;
limit_rate_after 5m;
limit_rate 250k;
}Apparently this will limit to 10 connections per IP. Here, perip is just the one name I have used. Be sure to add limit_conn_zone directive under httpd directive.
I was not able to make it work just because I am not aware of how Nginx searches the queries when we use location directive. More can be found from http://wiki.nginx.org/HttpCoreModule#location
Though it is mainly an Nginx thing instead of an ASPro thing. But symtab can put this to the documentation part of the forum if you feel like to do so ![]()
Thanks symtab. I am still finding a way to work it out. limit_conn works perfectly under "server". But it does not work under "location" ...
But it should work under "location" according to the documents....
I am now turning the server. Just wonder if I should try to limit the number of concurrent downloads per ip.
If so, how should I do it??
I am using nginx
And I try to use the limit_conn_zone directive
with limit_conn directive under
location /media/videos/mp4
location /media/videos/flv
location /media/videos/mobile
and
location /tmp/downloads
I try to limit it to 2 connections at a time but I can still download more than 3 videos at a time....
I am about to purchase a commercial license of flowplayer. However, I would like to know if there will be compatibility issue with ASPro if I purchase and download version 3.2.15 of flowplayer.
Or I can download earlier versions when I purchase??
Thanks!
With cache enable, cache driver File
Embed is not working, I have check the iframe.
Codes within the iframe becomes
<html>
<body>
<script type="text/javascript" src="http://www.mydomain.com/modules/video/player/config_iframe.php?id=451"></script>
<script type="text/javascript" src="http://www.mydomain.com/misc/flowplayer/flowplayer-3.2.11.min.js"></script>All other parts are missing.
However, it works perfectly when cache is not enable, or the cache driver is none.
Is it a bug or something?
It seems that we can only install the 1.0.x version of ffmpeg
There can be problem if we install version 1.2
Fixed. It is because the settings are written on a config file. I edit the config_xxxxxxxxxxxxxxxxxxxxx.php file and it is alright now.
I was experimenting with different settings.
After I set memcache for session, I was keep logging out.
I cannot login even I change the config table manually back to s:4:"none" for session_driver
There should be a lot of space on the server and I really do not know what happned....
Just solved the problem
It is the charset of the phpmailer. I changed it to utf-8 and it solved the problem.
Just find out that the same problem occurs for grabber
So I will suspect that it is a bug related to the timezone
Since I am not using english, fromname will not be displayed properly when users get confirmation emails for registration.
May I know which file is controlling the function to send the mails so that I can make some changes to it?
P.S. I have already make changes to /admin/module/email/component/send.php such that the fromname can be displayed properly when sending emails from admin.
Just tested. timestamp mixed again when using ftp upload after 13:00
date/time support enabled
"Olson" Timezone Database Version 0.system
Timezone Database internal
Default timezone Asia/Taipei
Yes it is the same as what I set.
Any suggestions for the sizes of the videos?
Thanks!
Just added another video, the timestap in add_time is 1363367273
which yields
GMT: Fri, 15 Mar 2013 17:07:53 GMT
GMT+8: Fri, 16 Mar 2013 1:07:53
As I expect, the timestamp is correct after 01:00. I guess the problem only occurs between 00:00 - 01:00 and 12:00 - 23:59. I will test it again after 12:00 noon and 13:00 (GMT+8). It seems that this only occurs when using FTP upload.