Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use

最新推荐文章于 2019-11-23 14:14:19 发布
最新推荐文章于 2019-11-23 14:14:19 发布
阅读量3.7k 收藏 1
点赞数 1
CC 4.0 BY-SA版权
分类专栏： php
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/resilient/article/details/82995748
本文介绍了三种在PHP中设置中国时区的方法：1. 在代码中使用date_default_timezone_set('PRC')；2. 修改php.ini配置文件，设置date.timezone为'Asia/Shanghai'；3. 在页头使用ini_set('date.timezone','Asia/Shanghai')。设置后需重启服务器。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

方法一:在代码中加入 date_default_timezone_set("PRC");即可

date_default_timezone_set('PRC')表示设置中国时区

方法二 :在配置文件php.ini中修改配置

在php.ini里加上找到date.timezone项，去掉前面的";"，添加设置date.timezone = "Asia/Shanghai"，北京的时间也写成上海那个。

 

方法三:在页头加上设置时区ini_set('date.timezone','Asia/Shanghai');

设置好后,都需要重启服务器

sudo apachectl restart

解决PHP程序提示日期函数依赖系统的时区设置是不安全的警告—Warning: date(): It is not safe to rely on the system‘s timezone setti
CoffeMilk的博客
12-23 296
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you mo
It is not safe to rely on the system's timezone settings
直到世界的尽头
05-05 1681
php项目 发布到服务器后  启动服务器  访问页面时报错  It is not safe to rely on the system's timezone settings 这是因为PHP所取的时间是格林威治标准时间，所以和你当地的时间会有出入格林威治标准时间和北京时间大概差8个小时左右，我们可以按照下面的方法解决：  1、在页头使用date_default_timezon
Warning: date(): It is not safe to rely on the system's timezone settings
云天空的博客
01-09 2333
在用PHP5.3以上的PHP版本时，只要是涉及时间的会报一个  Warning:  strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set
date(): It is not safe to rely on the system’s timezone settings
whyhonest的专栏
05-04 2022
PHP Warning: date(): It is not safe to rely on the system’s timezone settings 2011年10月25日admin发表评论阅读评论 通过观察nginx的错误日志，发现大量的如下错误： PHP Warning: date(): It is not safe to rely on the sys
date(): It is not safe to rely on the system's timezone settings
weixin_30588729的博客
11-16 140
部署MetInfo企业网站管理系统（php开源项目）时报此警告。 运行环境： Apache服务器 + MySQL5.5 + PHP5.4.5 函数 string date ( string$format [, int$timestamp ] ); 参考文档位置 date函数说明 it's a warning in PHP 5.4, looks like i...
[php] date(): It is not safe to rely on the system's timezone settings.
weixin_34368949的博客
11-12 111
date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. 出现这个问题，主要是因为没有在 php.ini 里面对时区进行设置造成的，...
PHP错误提示It is not safe to rely on the system……的解决方法
01-02
PHP Warning: date(): It is not safe to rely on the system’s timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of...
php报时区错误,按照网上说的改时间date.timezone根本不管用!怎么解决,看我的.zip
01-06
Warning: phpinfo() [function.phpinfo]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In ...
深入解析PHP 5.3.x 的strtotime() 时区设定 警告信息修复
12-18
然而，当你运行PHP 5.3.x版本的程序时，可能会遇到一个警告信息：“PHP Warning: strtotime(): It is not safe to rely on the system’s timezone settings...”。这个警告提示你不能依赖系统的时区设置，而是需要...
关于php程序报date()警告的处理(date_default_timezone_set)
12-19
PHP Warning: date(): It is not safe to rely on the system’s timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of...
date(): It is not safe to rely on the system’s timezone settings.
Eliot
10-31 1692
在执行php脚本时出现的错误： date(): It is not safe to rely on the system’s timezone settings.You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used an
【php】PHP Warning: date(): It is not safe to rely on the system's timezone settings.
行路中
09-26 4732
在执行php文件时会出现下面的警告：  PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use...
weixin_30314793的博客
12-17 250
错误截图 Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used a...
解决php的“It is not safe to rely on the system’s time
qq_23600817的博客
07-08 410
引用于:http://beikeit.com/post-682.html PHP调试的时候出现了警告: It is not safe to rely on the system解决方法,其实就是时区设置不正确造成的,本文提供了3种方法来解决这个问题。 实际上，从PHP 5.1.0开始当对使用date()等函数时，如果timezone设置不正确，在每一次调用时间函数时，都会产生E_
php异常 Message: date(): It is not safe to rely on the system's timezone settings
favoorr技术之路
08-27 1843
POST ajax_login 200 OK 172.16.12.76:8086 483 B 172.16.12.76:8086 107ms 头信息Post响应HTML缓存Cookies A PHP Error was encountered Severity: Warning Message:  date(): It is not safe to rely on the system
Warning: date() ：It is not safe to rely on the system's timezone settings
weixin_30664615的博客
11-22 294
在执行php文件时会出现下面的错误：PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In ca...
问题解决：Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You.
qq_40732189的博客
11-23 1231
在我们使用到时间函数data()时，有时候会弹出下面这种错误： “PHP Warning: date() [function.date]: It is not safe to rely on the system’s timezone settings. You are required to use the date.timezone setting or the date_default_t...
翻译： Of course. After reviewing your Gradle files, it's clear the main problem is not a single error but a mix of structural issues, outdated practices, and critical typos. Your build script merges settings that should be in separate files and uses fragile methods that will cause constant problems. Here is a breakdown of the issues and a step-by-step guide to fix them. ----- ### \#\# 1. Critical Errors That Will Break the Build These issues need to be fixed first, as they will prevent Gradle from running correctly. #### **A. Typo in `targetSdk`** In your module's `build.gradle`, you have a typo. * **Problem:** `targetsdk 34` * **Fix:** It should be `targetSdk` (with a capital 'S'). <!-- end list --> ```groovy // In your module's build.gradle defaultConfig { minSdk 29 targetSdk 34 // FIX: Was 'targetsdk' } ``` #### **B. Typo in JaCoCo Configuration** In your `createOfflineTestCoverageReport` task, you have a typo in the word "configurations". * **Problem:** `classpath: configur3+ations.jacocoAnt.asPath` * **Fix:** It should be `configurations.jacocoAnt.asPath`. <!-- end list --> ```groovy // In your JaCoCo task ant.taskdef(name: 'report', classname: 'org.jacoco.ant.ReportTask', classpath: configurations.jacocoAnt.asPath) // FIX: Was 'configur3+ations' ``` ----- ### \#\# 2. Major Structural Problems Your project's build logic is incorrectly structured. You've mixed settings for the root project and the `model_base` module into one file. #### **A. Root Project and Module Logic are Mixed** You should have at least two `build.gradle` files: one in the project's root directory and one inside your `model_base` module. * **Project Root `build.gradle` or `build.gradle.kts`:** Should contain `buildscript` settings (like the Android Gradle Plugin version) and `allprojects` repository settings. It should **not** contain `apply plugin: 'com.android.library'` or Android-specific settings like `compileSdk`. * **Module `app/build.gradle` or `library/build.gradle.kts`:** Should contain `plugins { id 'com.android.library' }`, the `android { ... }` block, and the `dependencies { ... }` for that specific module. #### **B. Action Plan: Restructure Your Files** **Step 1: Create a `settings.gradle` file in your project root** (if you don't have one). It tells Gradle which modules are part of your project. ```groovy // settings.gradle include ':model_base' // include ':app' // if you have an app module ``` **Step 2: Clean up your Root `build.gradle` file.** It should only contain build-wide information. ```groovy // Project Root: build.gradle // The buildscript block is an older pattern, but if you keep it: buildscript { repositories { google() mavenCentral() } dependencies { // Use a consistent version for AGP classpath 'com.android.tools.build:gradle:8.1.0' // You don't need JaCoCo here; the plugin handles it. } } allprojects { repositories { google() mavenCentral() maven { url "https://jitpack.io" } } } ``` **Step 3: Create/Fix your Module `model_base/build.gradle` file.** This is where most of your current code should go. ```groovy // Module: model_base/build.gradle // Use the plugins block at the top plugins { id 'com.android.library' id 'jacoco' // Apply jacoco plugin here } android { namespace 'com.st.model_base' compileSdk 34 defaultConfig { minSdk 29 targetSdk 34 // Corrected typo } // ... your other android settings } dependencies { // ... your dependencies implementation 'androidx.appcompat:appcompat:1.6.1' // Updated version } // ... your JaCoCo tasks and configuration ``` ----- ### \#\# 3. Bad Practices and Recommendations These are issues that make your build slow, fragile, and hard to maintain. #### **A. Manual `bootstrapClasspath` Manipulation is Very Bad** Your use of `options.compilerArgs << '-Xbootclasspath/p:...'` and manually rebuilding the `bootstrapClasspath` to include `framework.jar` is an extremely fragile and outdated practice. * **Why it's bad:** It overrides the standard Android compile environment. It can break with any update to AGP, Gradle, or Java. It makes your build completely dependent on a local JAR file. * **Recommendation:** **Remove all three `gradle.projectsEvaluated` blocks.** Rely on the `compileSdk 34` to provide the Android APIs. If you absolutely need APIs not available in the public SDK, this approach is still not recommended and indicates a potential design flaw. #### **B. `dependsOn(clean)` is an Anti-Pattern** Your line `createOfflineTestCoverageReport.dependsOn(clean)` is very inefficient. * **Why it's bad:** It forces a complete project clean and recompile **every time** you want to generate a report. This will make your build process incredibly slow. * **Recommendation:** **Delete this line.** Gradle's tasks are designed to be incremental. #### **C. Redundant Configurations** You have multiple `tasks.withType(Test)` and `gradle.projectsEvaluated` blocks. This makes the script confusing. * **Recommendation:** Combine them into single blocks to avoid conflicts and make the logic clear. #### **D. Outdated Dependencies and Repositories** * **JCenter is Deprecated:** Remove `jcenter()` from your repositories. It was shut down years ago and can slow down your build as Gradle tries to connect to it. `mavenCentral()` has replaced it. * **Old AppCompat Library:** `androidx.appcompat:appcompat:1.4.1` is old for `compileSdk 34`. Update it to a more recent version like `1.6.1` to avoid potential incompatibilities.
最新发布
07-24
当然。在查看了你的 Gradle 文件后，可以明确主要问题不是一个单一错误，而是结构性问题、过时做法和关键拼写错误的混合。你的构建脚本将应该放在不同文件中的设置合并到了一起，并使用了一些容易出错的方法，这会导致持续性的问题。 以下是问题的详细分析和逐步修复指南。 --- ### \#\# 1. 会导致构建失败的关键错误 这些问题是必须首先修复的，因为它们会阻止 Gradle 正常运行。 #### **A. `targetSdk` 中的拼写错误** 在你的模块 `build.gradle` 文件中存在一个拼写错误。 * **问题：** `targetsdk 34` * **修复：** 应该为 `targetSdk`（注意大写 'S'）。 ```groovy // 在你的模块 build.gradle 中 defaultConfig { minSdk 29 targetSdk 34 // 修复：原为 'targetsdk' } ``` #### **B. JaCoCo 配置中的拼写错误** 在你的 `createOfflineTestCoverageReport` 任务中，单词 "configurations" 的拼写错误。 * **问题：** `classpath: configur3+ations.jacocoAnt.asPath` * **修复：** 应该为 `configurations.jacocoAnt.asPath`。 ```groovy // 在你的 JaCoCo 任务中 ant.taskdef(name: 'report', classname: 'org.jacoco.ant.ReportTask', classpath: configurations.jacocoAnt.asPath) // 修复：原为 'configur3+ations' ``` --- ### \#\# 2. 重大结构性问题 你的项目构建逻辑结构不正确。你将根项目和 `model_base` 模块的设置混合到了一个文件中。 #### **A. 根项目和模块逻辑混合** 你应该至少有两个 `build.gradle` 文件：一个在项目根目录下，一个在你的 `model_base` 模块中。 * **项目根目录 `build.gradle` 或 `build.gradle.kts`：** 应包含 `buildscript` 设置（如 Android Gradle 插件版本）和 `allprojects` 的仓库设置。它 **不应该** 包含 `apply plugin: 'com.android.library'` 或像 `compileSdk` 这样的 Android 特定设置。 * **模块 `app/build.gradle` 或 `library/build.gradle.kts`：** 应包含 `plugins { id 'com.android.library' }`、`android { ... }` 块和该模块的 `dependencies { ... }`。 #### **B. 行动计划：重构你的文件** **步骤 1：在项目根目录下创建一个 `settings.gradle` 文件**（如果没有的话）。它会告诉 Gradle 项目中包含哪些模块。 ```groovy // settings.gradle include ':model_base' // include ':app' // 如果你有 app 模块 ``` **步骤 2：清理你的根目录 `build.gradle` 文件。** 它应该只包含构建范围的信息。 ```groovy // 项目根目录：build.gradle // buildscript 块是一个较旧的模式，但如果你保留它： buildscript { repositories { google() mavenCentral() } dependencies { // 使用一致的 AGP 版本 classpath 'com.android.tools.build:gradle:8.1.0' // 这里不需要 JaCoCo，插件会处理 } } allprojects { repositories { google() mavenCentral() maven { url "https://jitpack.io" } } } ``` **步骤 3：创建/修复你的模块 `model_base/build.gradle` 文件。** 这是你当前大多数代码应该去的地方。 ```groovy // 模块：model_base/build.gradle // 在顶部使用 plugins 块 plugins { id 'com.android.library' id 'jacoco' // 在这里应用 jacoco 插件 } android { namespace 'com.st.model_base' compileSdk 34 defaultConfig { minSdk 29 targetSdk 34 // 修复了拼写错误 } // ... 你的其他 android 设置 } dependencies { // ... 你的依赖项 implementation 'androidx.appcompat:appcompat:1.6.1' // 更新了版本 } // ... 你的 JaCoCo 任务和配置 ``` --- ### \#\# 3. 不良实践和建议 这些问题会使你的构建缓慢、脆弱且难以维护。 #### **A. 手动操作 `bootstrapClasspath` 是非常糟糕的做法** 你使用了 `options.compilerArgs << '-Xbootclasspath/p:...'` 并手动重建 `bootstrapClasspath` 来包含 `framework.jar`，这是一种极其脆弱且过时的做法。 * **为什么不好：** 它会覆盖标准的 Android 编译环境。它可能在 AGP、Gradle 或 Java 任何一次更新中失败。它会使你的构建完全依赖于本地 JAR 文件。 * **建议：** **删除所有三个 `gradle.projectsEvaluated` 块。** 依赖 `compileSdk 34` 来提供 Android API。如果你确实需要公共 SDK 中不可用的 API，这种方法仍然不推荐，并且表明可能存在设计缺陷。 #### **B. `dependsOn(clean)` 是反模式** 你的 `createOfflineTestCoverageReport.dependsOn(clean)` 这一行效率非常低。 * **为什么不好：** 它强制每次生成报告时都要完全清理和重新编译整个项目。这会使你的构建过程变得极其缓慢。 * **建议：** **删除这一行。** Gradle 的任务是为增量构建设计的。 #### **C. 冗余的配置** 你有多个 `tasks.withType(Test)` 和 `gradle.projectsEvaluated` 块。这会使脚本变得混乱。 * **建议：** 将它们合并到单一的块中，以避免冲突并使逻辑更清晰。 #### **D. 过时的依赖和仓库** * **JCenter 已被弃用：** 从你的仓库中移除 `jcenter()`。它几年前就已经关闭了，并且 Gradle 会尝试连接它，从而减慢你的构建速度。`mavenCentral()` 已经取代了它。 * **旧的 AppCompat 库：** `androidx.appcompat:appcompat:1.4.1` 对于 `compileSdk 34` 来说已经过时了。将其更新到更新的版本如 `1.6.1` 以避免潜在的不兼容问题。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

芝麻开门2015

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值