Jump to content
The Krotek Support Forum
  • Sign Up

The Shadow

Members
  • Content count

    18
  • Joined

  • Last visited

About The Shadow

  • Rank
    Member
  1. The Shadow

    Posting time

    I found solution as it runs on a virtual Ubuntu machine. By timedatectl I can change the time zone of the virtual machine to match Russian time.
  2. The Shadow

    Posting time

    Posted on Jooma : 19:30 Moscow time (17:30 CET) Posted on Networks 21:30 Moscow time (19:30 CET) Joomla setting: Moscow time (+2H) If I change Joomla server time the website will not work on Russian time.
  3. The Shadow

    OK posting mystery

    Same thing, success but no post number. I did notice in the log when a post goes it gives post number, when not it only tells success.
  4. The Shadow

    Posting time

    I have another issue, should be simple to fix. When article is üsted at 19:30 website time it appears 2 hours later. Probable cause: website time is on Moscow time but webservers is located in France (Central European time). Difference is 2 hours, or 3 hours after Sunday. We would like to keep site on Moscow time, but not wait 2 hours for the article.
  5. The Shadow

    OK posting mystery

    From the other post I noticed to limit posting to 1000 characters. Is the limit field in words or characters? I tried several options but even 300 or 250 do not work. Please check and if limit is in words fix in next update.
  6. The Shadow

    OK posting mystery

    I have been checking the API. Do not worry I am way too lazy, I mean busy, to write code myself. But I noticed with my limited Russian that the API seems to be based on message sharing. On this there is a limit, it is 230 or 250 charaters. As I am testing if I find the correct limit I will tell.
  7. The Shadow

    OK posting mystery

    It seems that there is a post limit on big text.If we take away all except the first sentence the article does post.Perhps there is a limit that is not retuning an error.
  8. The Shadow

    OK posting mystery

    Sorry for long reply, busy day at work. Here are screenshots.
  9. The Shadow

    OK posting mystery

    It says success
  10. The Shadow

    OK posting mystery

    We have a bit of a mystery. The post in the attached file is an article. When posting to ok.ru logs show as sucess. But there is no post number and the post does not appear. We have tried with word limit of 300 and 450 but no change. Facbook, vK and twitter work, the return a post number, also when the post contains an image. other posts on OK do work and return a post number. Any idea what can be wrong. okupost.txt
  11. The Shadow

    VK and OK paramter problems.

    Do not see result of the meta tags. However the cron does not ive output but breaks down. Good thing is ok.ru is working perfect, which is most imporant. When there is a new question I will ask you. Thank you for your help, I appreciate you are replying at almost all hours.
  12. The Shadow

    VK and OK paramter problems.

    Nearly there. Twitterm vKontate work. Odnoklassniki waiing for support to get in to office nad give permisions. Facebook does post but without image. We try a animated gif of 3Mb. Is this permission problem or other problem?
  13. The Shadow

    VK and OK paramter problems.

    Sorry for mistakes in spelling. Am I corrct you use Google translate and can not read English? If os I will ask a friend to translate to Russian. I thank you for fast answers and will not give up until all works perfct.
  14. The Shadow

    VK and OK paramter problems.

    Update: a server restart did ause some progress. vKontakte is now posting, after the firt issue was solved there was an error in group permissions which was solvd by recreating the app. Odnoklassniki I will wait for the support to handle the permissions mail and see if after that things will work if not go over all parameters again. Twitter posted once and then went back to global error 32. Bck to the drawing board and re-check all.
  15. The Shadow

    VK and OK paramter problems.

    While I can make errors, copyng and pasting keys and ensuring no spacs are eft is not something I usually do wrong. Twitter also refused authentication, where as on th test site it worked without an issue. When searching the error on Google I came to something that seems a recurring issue: time. According to the article the OAuth method includes a time. The server of the website is located in France. The test site had no time correction however the main site is on Moscow time. Both sites are on similar though separate virtual machines running on the same dedicated server. I upgraded ntp in order to see if that solves the issue. The test site and main do have different twitter accounts, but the app settings are equal and I have ensured once again no spaces or other things are present on either side of anz of the keys. Any suggetions ?
×