WordPress 中的 jQuery 循环中断
有什么想法可以解释为什么 jQuery Cycle 插件在本地安装的 WordPress 上可以完美运行，但现在在实时服务器上运行却无法正常运行吗？我已经在 wordpress 标头中引用了所有 javascript 文件，并且所有循环函数都编写在“custom.js”中。我知道最好的做法是将这些内容包含在页脚中，但这似乎给我带来了错误。
http://sameralmadani.com/aleo_retouching/?page_id=6
关于为什么.cycle() 插件被忽略将不胜感激。
Any ideas as to why the jQuery Cycle plugin would function perfectly on a local install of wordpress and is now broken running on a live server? I have referenced all of my javascript files in the wordpress header and all of my cycle functions are written in "custom.js". I understand that it is best practice to include these in the footer but this seemed to give me errors.
http://sameralmadani.com/aleo_retouching/?page_id=6
Any clue as to why the .cycle() plugin is getting ignored would be much appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您必须更改服务器/FTP 设置。
您无权访问 http ://sameralmadani.com/aleo_retouching/wp-content/themes/twentyeleven/js/jquery.cycle.all.min.js 因为403 错误。
将 /wp-content 文件夹（递归）设置为 CHMOD 777。如果有效，请将 CHMOD 设置回 755 并检查它是否也有效。
有关更多信息，请参阅 https://stackoverflow.com/a/2785552/1184904
You have to change your server/ftp settings.
You don't have access to http://sameralmadani.com/aleo_retouching/wp-content/themes/twentyeleven/js/jquery.cycle.all.min.js because of a 403 error.
Set the /wp-content folder (recursive) to CHMOD 777. If this works, set CHMOD back to 755 and check if it works too.
See https://stackoverflow.com/a/2785552/1184904 for further information
您的网站显然无法访问“cycle”和“easing”js 所在的位置。
它给出了“403 Forbidden”错误。 http://en.wikipedia.org/wiki/HTTP_403
Your site apparently doesn't have access to the location where your "cycle" and "easing" js is located.
It's giving a "403 Forbidden" error. http://en.wikipedia.org/wiki/HTTP_403
您使用的是 Cycle 的 WordPress 插件版本吗？您是否在控制面板中指定了父容器的id名称？如果您刚刚将网站迁移到新网址，则该信息可能不会保留。
Are you using the WordPress plugin version of cycle? Have you specified the parent container's id name in the control panel? If you just migrated your site to a new url that information may not have been retained.